monitoring issues

Errors are grouped into issues by fingerprint. This lists them with each one's level, status, how many events and users it has, and when it was last seen. See issues.

octri monitoring issues [--status <status>] [--level <level>] [--q <text>]

Flags

--range <window>stringdefault: 24h

The time window: 1h, 6h, 24h, 7d, 30d or 90d.

--status <status>string

Only unresolved, resolved or ignored issues.

--level <level>string

Only one level, such as error or warning.

--q <text>string

Searches the issues, such as --q checkout.

--sort <order>string

The order, as the dashboard's issue list sorts.

--limit <n>numberdefault: 25

How many to show.

Examples

Unresolved errors

octri monitoring issues --status unresolved --level error

✔ Loading issues

Issues (3 of 3)
  ID        LVL    TITLE                                        EVENTS  USERS  STATUS      LAST SEEN
  ────────  ─────  ───────────────────────────────────────────  ──────  ─────  ──────────  ─────────
  7224d822  error  ValidationError: currency must be a <num>-…  45      15     unresolved  2h ago
  aa9cb950  error  CheckoutUnavailableError: The payment prov…  3       3      unresolved  5h ago
  98190f2e  error  TypeError: Cannot read properties of undef…  8       1      unresolved  7h ago
  octri monitoring issue <id>: full stack trace

octri monitoring issue: One issue with its status, release, culprit and stack trace.
octri monitoring resolve: Mark an issue resolved. If it happens again, it's a regression.
octri monitoring logs: Query individual events, newest first, when you need every occurrence.

Flags

Examples

Unresolved errors

Related