Console Guides

Monitoring

Monitoring is the operational health view for your project: a usage snapshot, request performance, an audit log of account and infrastructure actions, and threshold-based alerts - across four tabs.

Find it

Monitoring is in the sidebar under the Operations group.

Overview

The Overview tab opens on four tab buttons (Overview, Audit Logs, Errors, Alerts) and a Refresh control that re-fetches every source on the tab you are currently viewing.

Three stat cards sit below them: success rate and avg response time, both derived from request performance data over the selected window, and active alerts, which counts alerts with isActive true.

Beneath the cards, the usage and performance panel shows API calls and storage for the selected window, followed by request counts, error counts and a daily breakdown.

Audit Logs

Monitoring Audit Logs tab with the Action, Resource, and User ID filters, Apply filters button, and the log table marked
Audit Logs - a running record of account and infrastructure actions
  1. Narrow by Action (e.g. backup.create, api_key.create), Resource, or a specific User ID.
  2. Click to apply the filters above; clearing the fields and applying again resets to page 1.
  3. Each row shows when an event happened, a human-readable activity title and detail, the machine action string, which user triggered it, and which project it belongs to. Actions like backup.create and data.delete land here automatically - you don't configure what gets logged.

Errors

Monitoring Errors tab with the error types breakdown card and the error log table marked
Errors - grouped error types alongside the raw event log
  1. A count per distinct error/event type recorded for this project, most useful for spotting one type spiking.
  2. The same events as a paginated table - time, type, endpoint (when recorded), user, and project. A quiet project can legitimately show no rows here.

Alerts

Monitoring Alerts tab with the alerts table and the create alert form marked
Alerts - existing alerts on the left, the create form on the right
  1. Name, condition, threshold, notification action, and whether the alert is active. Conditions and thresholds are free text/number - there's no fixed enum, so name them descriptively (e.g. api_error_rate at threshold 25).
  2. Pick the project the alert applies to, set a condition, threshold, and action (e.g. email), then click Create alert. Alert count per project is capped by your plan - the form disables with a limit message once you're at capacity.
Note
The Errors tab and the Analytics page's error distribution share the same underlying event data - cross-check there for the same events grouped by time period instead of by type.
Chat with us