Interface: EntryFilter

Defined in: types/entry.types.ts:381

What find narrows by.

It used to declare thirteen more fields under a heading that said "advanced filtering", and no storage read any of them: a caller could ask find for { method: 'POST', statusCodeMin: 500 } and receive every entry there is, with nothing to say the request had been ignored. Narrowing beyond this is findWithCursor's filters, which every backend applies before it chooses a page — and which is checked against all three in the parity suite.

Properties

from?

optional from: Date

Defined in: types/entry.types.ts:384

---

limit?

optional limit: number

Defined in: types/entry.types.ts:386

---

offset?

optional offset: number

Defined in: types/entry.types.ts:387

---

requestId?

optional requestId: string

Defined in: types/entry.types.ts:383

---

to?

optional to: Date

Defined in: types/entry.types.ts:385

---

type?

optional type: "query" | "request" | "exception" | "log" | "cache" | "event" | "job" | "schedule" | "mail" | "http-client" | "redis" | "model" | "notification" | "view" | "command" | "gate" | "batch" | "dump" | "graphql"

Defined in: types/entry.types.ts:382