Monitoring, Errors, and Session Replay

Analytics doesn't just chart your data — it watches your product. This page covers the Monitoring tab (uptime checks and error triage), session replay, and traffic/SEO reporting. It's useful to anyone using Analytics, though a few sections get more technical toward the end.

Uptime monitoring

Add a monitor for any URL: pick the HTTP method, an interval (checked every few minutes), an expected status range or exact codes, and optional assertions (response body contains X, a header matches, latency stays under a threshold). When a check fails, Analytics opens an incident, applies a cooldown so it doesn't spam you on every retry, and notifies you through the inbox, email, Slack, or a webhook — configurable per monitor.

Ask the agent directly: "add an uptime check for api.example.com/health every 5 minutes, alert Slack if it goes down" — no dashboard-building required.

Public status pages. Bundle a set of your monitors under a public page at /status/<your-slug> — anyone with the link sees color-coded uptime bars and overall uptime percentages, never the underlying URLs, headers, or alert configuration, unless you explicitly opt a monitor in to show its URL. You control the layout: which of uptime bars, overall uptime, and response time show, plus a comfortable or compact density.

Error issue triage

Browser exceptions captured from your app (or from Analytics itself) get grouped into issues by a stable fingerprint — one row per distinct error, not one row per occurrence. Each issue tracks its type, a human-readable title, severity (fatal down to debug), first-seen and last-seen times, a lifetime occurrence count, and roughly how many distinct users hit it.

Open an issue to see recent frequency, a parsed stack trace (with source snippets where available), breadcrumbs leading up to the error, tags, and — when one exists — a link to the session recording where it happened. Mark an issue resolved or ignored once you've dealt with it; it reopens automatically if it recurs.

Session replay

Every recorded session captures the page, a masked/privacy-aware view of user interactions, console output, and network activity, then plays it back frame by frame. Inputs are masked by default; mark any element .an-mask (hide the text) or .an-block (skip capture entirely) for anything more sensitive.

The replay player has a Dev Tools toggle with Console and Network tabs — filter chips, search, an error-count badge, and click-to-jump so you can seek the playhead straight to the moment a request failed or an error logged. It's built for the exact workflow of debugging a user-reported bug: search their email on the Sessions list, open their recording, and jump straight to the failure.

Sharing a replay with an external agent. Recordings stay private — Analytics never makes one public just so an agent can look at it. Instead, open the session and click Copy for agent to mint a two-hour tokenized link. Paste that link to any agent and it can read a bounded, redacted diagnostics feed (console and network entries, errors first) without ever seeing raw replay storage:

GET /api/session-replay/agent-context.json?id=<recordingId>&agent_access=<token>
GET /api/session-replay/agent-diagnostics.json?id=<recordingId>&agent_access=<token>&kind=console|network|all
GET /api/session-replay/agent-events.json?id=<recordingId>&agent_access=<token>

Traffic and SEO

Two more read-only data surfaces round out this tab:

• SEO metrics, once a DataForSEO connection is configured — top-ranked keywords across your blog, and ranked keywords for one page by slug.
• First-party marketing dashboards built from the same event stream everything else in Analytics uses — signups, template/feature clicks, referral sources, and viral coefficient. Analytics ships a worked example dashboard demonstrating this pattern that you can open directly or copy as a starting point for your own.

What's next

• Dashboards, Analyses, and the Data Dictionary — the other place you'll spend time day to day
• Connecting and Extending Data Sources — connecting DataForSEO and the rest of your stack
• Extending Analytics — the monitoring/error/session schema and action reference
• Analytics overview — back to the app summary