Enori Documentation
Whether you're setting up your first monitor, tuning alerts, or documenting reliability for a customer SLA, you'll find what you need here.
Getting started
Concepts
Service Level Objectives
Track reliability against measurable targets, get alerted when burn rate is unhealthy, generate customer-facing SLA reports.
Distributed Traces
Send OpenTelemetry traces from your app to debug latency and errors span by span — with a service map, RED health charts, RED alerts, and AI root-cause analysis.
Uptime Reports
Generate on-demand uptime and SLA reports for any period, export them to PDF or CSV, and share a public link — with accurate, maintenance-excluded metrics.
Audit Log
Every configuration change on your account is recorded automatically — who did what, when, and from which IP. Filter, search, and export your audit history to CSV.
Jobs Overview
See every cron job and scheduled task in one place — live Up/Down/Late status, a month calendar of runs, and a day-by-day timeline, all shown in UTC.
Timeline
One calendar for every event across all your monitors — incidents, maintenance, cron runs, alerts, SSL and domain expiries, and config changes. Export a range or subscribe from your calendar app.
Reference
API Reference
REST API for programmatic monitor, incident, alert, and status-page management.
MCP Server
Drive Enori from Claude Desktop, Claude.ai, or any MCP client. OAuth-or-API-key auth, 57 tools covering monitors, incidents, alerts, status pages, browser checks, and SLOs.
Monitoring IP Addresses
Static source IPs for browser (synthetic) checks — add them to your firewall, IP allowlist, or bot-protection rules so our monitors can reach you.
Spot an error or want a new topic covered? Email support@enori.io.