Skip to content

Issues and alerts

How browser errors are grouped into issues, how issues are resolved, ignored and reopened by a newer release, their counts and session timelines, and alerts on new and regressed issues.

Updated View as Markdown

An issue is one kind of error in one environment and application: every error with the same fingerprint. Instead of a list of thousands of errors, you get the few problems behind them, each with its counts, its symbolicated stack trace, the breadcrumbs that led to it, and a state you manage.

  • The title is the first event’s type and message, such as TypeError: Cannot read properties of undefined (reading 'price').
  • The culprit is the top frame of your own code: its function and file, such as CartSummary (src/cart/CartSummary.tsx).
  • Each issue has an ID, an iss_ slug and a resource name. Its ID is in the ezgh.rum.issue.id attribute of every error it groups.
The Issues page for the production environment over 24 hours, sorted by last seen: Unresolved, Resolved and Ignored tabs, and 20 issues, each with its title and culprit, events, users, a sparkline, first and last seen and first release; two carry a Regressed badge.The Issues page for the production environment over 24 hours, sorted by last seen: Unresolved, Resolved and Ignored tabs, and 20 issues, each with its title and culprit, events, users, a sparkline, first and last seen and first release; two carry a Regressed badge.

How errors are grouped

Each error’s fingerprint is, in order:

  1. the string you gave with captureException(error, { fingerprint: "checkout-timeout" });
  2. otherwise, the error type and your code’s top 5 frames, by function and file, not line or column, so a new build keeps the same issues;
  3. otherwise, when no frame is your code, the error type and the message with quoted strings, IDs, long hex values and numbers removed.

Frames from node_modules, the bundler’s runtime and scripts from origins the token doesn’t allow aren’t your code. Fingerprints are computed on symbolicated frames, so errors that arrive before their release’s source maps may form a separate issue: upload maps before you deploy.

States

State Meaning
Unresolved New and reopened issues
Resolved Fixed. It reopens as regressed when the error happens again in a release first seen after you resolved it
Ignored Never reopens

Events are counted in every state.

A resolved issue doesn’t reopen for errors from old tabs still running a release EZGH had seen before you resolved it: only a newer release reopens it. An event without a release reopens it too, so set release in init. Resolving an issue clears its regressed mark.

Counts and breakdowns

An issue’s events, users (by the setUser ID) and sessions are counted over a window: the last hour, 24 hours, 7 days or 14 days. Its breakdowns by release, browser, device, country and URL path show what its errors have in common, and its events list each error, newest first.

An issue's page, unresolved and regressed, with Ignore and Resolve buttons and a warning that source maps are missing for release 2026.10.13-4f2a9c1: its culprit, application, environment, first and last seen, events in 24 hours, fingerprint and iss_ ID, an events chart, and the Event tab: one event's time, release, browser, OS, device, country, URL, view and user, View trace and Session timeline buttons, the symbolicated stack with the source lines around the failing line, the breadcrumbs before the error, and its attributes.An issue's page, unresolved and regressed, with Ignore and Resolve buttons and a warning that source maps are missing for release 2026.10.13-4f2a9c1: its culprit, application, environment, first and last seen, events in 24 hours, fingerprint and iss_ ID, an events chart, and the Event tab: one event's time, release, browser, OS, device, country, URL, view and user, View trace and Session timeline buttons, the symbolicated stack with the source lines around the failing line, the breadcrumbs before the error, and its attributes.

Session timelines

From an event, Session timeline shows that session around the error: each view with its Web Vitals, the page loads, route changes, interactions and requests (with their status and duration), and errors, in order. View trace opens the event’s trace. A timeline shows up to 2,000 items nearest the error.

A session timeline: the session's ID, start, length, views, errors, browser, device and country, then three views (/, /cart and /checkout), each with its Web Vitals, listing the page load or route change, requests with status and duration, clicks, and a TypeError highlighted in red in /cart.A session timeline: the session's ID, start, length, views, errors, browser, device and country, then three views (/, /cart and /checkout), each with its Web Vitals, listing the page load or route change, requests with status and duration, clicks, and a TypeError highlighted in red in /cart.

Alerts

An issue alert rule notifies its contact points when an issue is created or regressed:

{
  "name": "New storefront errors",
  "condition": {
    "issue": {
      "datasetIds": ["0199a3b4-2c1d-7e5f-8a9b-1c2d3e4f5a6b"],
      "applications": ["storefront"],
      "on": ["created", "regressed"]
    }
  },
  "contactPoints": ["01990c3e-5f2a-7b1d-9c4e-2a6f8d0b1e37"]
}
Field Value
datasetIds 1 to 20 environments’ dataset IDs
applications 0 to 20 applications. Absent or empty: every application
on created, regressed, or both
  • It sends one notification per new or regressed issue, as it happens, with the issue’s title, culprit, application, environment, release and a link to it. It’s not evaluated every minute, so for and keepFiringFor must be 0m (the default), annotations aren’t allowed, and noData and repeatInterval don’t apply. There’s no preview (alert-rules/test) for it.
  • Creating or changing one needs obs.issues.list on each of its datasets.
  • In the console, choose Issues as the rule’s condition, or click Alert on new issues on the Issues page.
  • For “more than 100 events of one issue in 5 minutes”, use a logs condition on ezgh.rum.issue.id:
{
  "name": "Cart price errors spiking",
  "condition": {
    "logs": {
      "dataset": "0199a3b4-2c1d-7e5f-8a9b-1c2d3e4f5a6b",
      "filter": { "attributes": [{ "scope": "record", "key": "ezgh.rum.issue.id", "op": "equals", "value": "adeb358d-aceb-73fa-8beb-3267aaeb30d4" }] },
      "aggregate": { "fn": "count" },
      "window": "5m",
      "threshold": { "op": ">", "value": 100 }
    }
  },
  "noData": "ok",
  "contactPoints": ["01990c3e-5f2a-7b1d-9c4e-2a6f8d0b1e37"]
}
Creating an alert rule with the Issues condition: environments (production checked), applications (storefront checked), and notify when a new issue appears and when a resolved issue comes back in a newer release, then the contact points.Creating an alert rule with the Issues condition: environments (production checked), applications (storefront checked), and notify when a new issue appears and when a resolved issue comes back in a newer release, then the contact points.

Retention

An issue is deleted 30 days after its environment’s logs retention has passed its last event. Its errors are logs, kept by the dataset’s retention class like any other.

In the console, the CLI and the API

Open Observability > Real user monitoring > Issues. Choose the environment, application, window and sort; the tabs are Unresolved, Resolved and Ignored. An issue’s page has Resolve, Ignore or Unresolve at the top, an events chart, and the Event (one event with its stack, breadcrumbs and attributes, stepping through older and newer events), Distributions and Events tabs. The stack shows your code’s frames with the lines around them; All frames shows library frames too, and the minified stack is below.

ezgh obs issues list --environment production
ezgh obs issues list --environment production --application storefront --window 7d --sort users
ezgh obs issues get iss_c4rtpr1c3000 --events 10
ezgh obs issues resolve iss_c4rtpr1c3000
ezgh obs issues ignore iss_c4rtpr1c3000
ezgh obs issues unresolve iss_c4rtpr1c3000
  • list takes --dataset or --environment, and --application, --state (unresolved, the default, resolved, ignored or all), --release (the release an issue was first seen in), --window (1h, 24h, 7d or 14d) and --sort (events, the default, users, lastSeen or firstSeen). A regressed issue shows as unresolved (regressed).
  • get, resolve, ignore and unresolve take the issue’s ID or iss_ slug.

ezgh obs issues lists every flag.

Under /v1/organizations/<organization ID>/projects/<project ID>/obs/ at https://obs.ezghcloud.com. An issue is named by its ID or its iss_ slug.

Operation Request
List issues GET issues?datasetId=…, with application, state, release, window, sort, cursor and limit
Get an issue GET issues/<issue>
Change its state PATCH issues/<issue> with { "state": "resolved" } and If-Match
Break it down POST issues/<issue>/aggregate with { "window", "groupBy", "interval" }
List its events GET issues/<issue>/events
A session’s timeline POST sessions/<session ID>/timeline with { "datasetId", "around", "window" }
  • GET issues answers each issue with its events, users and sessions over the window and series: 24 event counts, oldest first, for a sparkline.
  • An issue’s version changes only when its state does, never when it’s seen again, so a PATCH with the ETag from GET is answered 412 precondition_failed only when someone else changed its state in the meantime.
  • aggregate groups by one field: service.version, browser.name, device.type, geo.country.iso_code or url.path (groupBy is required), and answers the top 20 groups with their events and users, and the events per interval.
  • A session timeline reads around ± window (1m to 4h, 4h by default), and answers up to 2,000 items with truncated when there were more.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close