Start here

Getting started

Use this guide when you are setting up AImonitoring for the first time or evaluating the product for a production rollout.

Audience: New users, founders, engineering leads

Recommended setup path

Create your account and open the dashboard.
Add one HTTP monitor for a customer-facing endpoint.
Create at least one alert channel so failures reach the right place.
Create a service and link the monitor to that service.
Add an SLO for the service if it is customer-facing or business-critical.
Invite team members and assign owner, admin, or member roles.
Publish a status page when you want customers or internal stakeholders to see health.

Monitors: synthetic checks for endpoints, ports, hosts, cron jobs, and AI agents.
Services: service catalog, owners, linked monitors, dependencies, and SLOs.
Incidents: service incidents, acknowledgements, notes, resolution, and reviews.
Telemetry: logs, metrics, traces, and agent run data.
Routing: escalation policies, maintenance windows, on-call schedules, and overrides.
Analytics: service health scoring, SLO burn signals, deployment correlations, MTTR, and root-cause groups.
Reports: export reliability, SLO, incident, and audit evidence.
Integrations: configure and verify incident response, workflow, deployment, telemetry, and automation providers.
Policies: retention, provider allow-lists, audit export controls, and tenant lifecycle requests.
Team & access: organization roles, permission overrides, invitations, and service team membership.
Audit log: access, configuration, incident, review, and API key history.

Monitor every customer-facing endpoint and critical background job.
Route critical service incidents to a channel that is watched outside normal business hours.
Create maintenance windows before planned work.
Confirm alert delivery with the test alert action.
Use service dependencies to document upstream risk and downstream blast radius.
Review the audit log after making access, API key, routing, or alerting changes.