Skip to main content

See What Is Happening

See What Is Happening​

Sign in with event-read access and open Monitoring (/monitoring). Read the tenant activity counters and evaluated alert feed. These counters describe your tenant; they are not a platform health verdict.

  1. Confirm the tenant and reporting time range.
  2. Inspect unexpected activity or alerts, then follow the relevant receipt in Ready data.
  3. Follow the server's bounded next action. If platform intervention is required, give support the tenant, time range, request/receipt ID and redacted warning.

Example: if a sent batch is missing from Events, check its accepted receipt before resending. Processing may still be underway. Expected result is ready coverage or an explicit next action, not an inference from a successful send alone.

Empty counters are not proof that every pipeline stage is healthy. Retry a failed read with the displayed retry control; preserve any request ID if it keeps failing.

Tenant API surfaces:

  • GET /api/v1/monitoring/summary
  • GET /api/v1/monitoring/alerts

System administrators have separate System status and Diagnostics views. The following diagnostics routes require platform authority:

  • GET /api/v1/diagnostics/ingest
  • GET /api/v1/diagnostics/buffers
  • GET /api/v1/diagnostics/database
  • GET /api/v1/diagnostics/segments
  • GET /api/v1/diagnostics/reporting

The frontend diagnostics page mirrors those sections for system admins.