Use this implementation map when building or debugging a monitoring interface. It points to the UI, server logic, data schema, scheduled jobs, and actions behind uptime checks, public status pages, and grouped error triage.
Implementation map for the Monitoring tab (uptime checks, public status pages, error triage): component/server file locations, schema, jobs, and scheduler wiring. Use when building or debugging Monitoring UI, uptime checks, status pages, or error capture/grouping — not when just calling the monitoring actions from chat.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
/monitoring is a thin shell (app/routes/monitoring._index.tsx →
app/pages/monitoring/MonitoringPage.tsx) hosting two independently-owned
panels selected by ?view=uptime|errors (defaults to uptime). navigation
mirrors it as view="monitoring" with monitoringView (plus
monitorId/errorIssueId when a row is open); each panel also writes richer
selection to the monitoring application-state key.
app/pages/monitoring/UptimePanel.tsx, app/pages/monitoring/uptime/**.server/lib/uptime-monitors.ts (checks/alerting), sweep job
server/jobs/uptime-monitors.ts, scheduler
server/plugins/uptime-monitor-jobs.ts, schema
server/db/schema-monitoring.ts.list-monitors, get-monitor, save-monitor, run-monitor-check,
delete-monitor.?view=uptime, detail ?view=uptime&monitor=<id>, create
?view=uptime&monitor=new, edit ?view=uptime&monitor=<id>&edit=1.docs/uptime-monitoring.md.app/pages/monitoring/uptime/status-pages/**, a config sub-view under
Uptime that bundles chosen monitors under a public /status/<slug> page.server/lib/status-pages.ts over server/db/schema-monitoring.ts.list-status-pages, get-status-page, save-status-page,
delete-status-page, add-status-page-monitor,
remove-status-page-monitor, reorder-status-page-monitors, plus the
unauthenticated get-public-status-page.?view=uptime&statuspage=list, create
?view=uptime&statuspage=new, edit ?view=uptime&statuspage=<id>.app/pages/monitoring/ErrorsPanel.tsx, app/pages/monitoring/errors/**
— first-party, Sentry-style exception triage grouped into issues by
fingerprint.server/lib/error-capture.ts over
server/db/schema-errors.ts.configureTracking() as $exception
events; server captureError() failures arrive through the shared tracking
provider when the server Analytics key is configured and use the same grouped
issue store.list-error-issues, get-error-issue, resolve-error-issue,
capture-test-error, match-error-issues.@agent-native/core/client
(captureException / captureMessage / addErrorBreadcrumb),
auto-enabled by configureTracking and transported through the first-party
analytics ingest as a $exception event.isTestIdentity) keep their exceptions:
occurrences are flagged testIdentity, never count toward users affected,
and never alert. An issue only they have hit is testIdentityOnly and hidden
from list-error-issues unless includeTestIdentities: true; the new-issue
alert fires on its first real-user occurrence instead. Ingest decides from
the identities an event carries (userId, email fields, its context), never
from a sender's test_identity flag, which any write-key holder could set.?view=errors&issue=<id>. Issue detail includes recent
frequency, parsed/raw stack traces, source code snippets when available,
breadcrumbs, tags, occurrence history, and session replay links.list-error-issues first, then get-error-issue for
stack, occurrence, and replay detail. These are separate from the external
Sentry action and do not require a Sentry credential.docs/error-capture.md.A recording's devtools Console error lines link to the grouped issue at
/monitoring?view=errors&issue=<id>, resolved by match-error-issues (exact
fingerprint match, no heuristics); issues link back to the originating
recording at /sessions/<recordingId>. The fingerprint includes the app, so
match-error-issues takes the recording's app and only matches issues filed
under it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate, refine, export, and place brand images or videos from an Assets library into another app. The skill covers choosing a library, handling image batches and video runs, and updating selected assets after feedback.
Prepare a customer account health, renewal, or contract usage readout. Verify the account identity, use approved metric definitions, compare contracted capacity with actual usage, and trace findings to sources, time windows, and known gaps.
Create focused app actions that agents can call as tools and frontend code can use through client hooks. Use them to add provider integrations or fetch UI data, with validated inputs and structured results.
Use this checklist when adding a feature or integration to an agent-native app. It covers the user interface, agent-callable actions, instructions, and app-state sync so both the user and agent can work with the capability consistently.
Investigate complex questions by combining data from multiple sources, then summarize patterns, metrics, and evidence in a clear report. Save requested analyses as dashboards with instructions for future refreshes.
Use the Analytics admin surfaces to inspect and change workspace feature flags, review dashboard ownership and usage activity, or browse and edit databases connected from other agent-native apps. The skill guides administrators to the relevant view and actions.