Public Status Page
Configure a public status page with real-time incident visibility, embeddable widgets, and badge SVGs.
Public Status Page
Obtrace includes a hosted status page that reflects real-time incident state for your services. When an incident is detected, the status page updates automatically based on impact scoring. No manual status updates are required unless you want to override the automated state.
Obtrace is an AI-powered observability platform that detects production errors, finds root causes automatically, and suggests or opens code fixes as pull requests. The status page is the public-facing layer of this detection pipeline.
Setup
Create a status page
Navigate to Settings > Status Page or use the API:
Custom domain
Point a CNAME record to status-pages.obtrace.dev and set custom_domain in the configuration. TLS is provisioned automatically via Let's Encrypt.
Service mapping
Each service listed on the status page maps to a monitored service tag in your telemetry. Status is derived from active incidents:
| Incident severity | Displayed status |
|---|---|
| No active incidents | Operational |
| Warning-level incident | Degraded Performance |
| Error-level incident | Partial Outage |
| Critical incident | Major Outage |
You can override any service status manually through the dashboard or API.
Embed widget
Add a floating status widget to your application:
The widget shows a small indicator that expands on click to show current service status.
Badge SVG
Embed a status badge in your README or documentation:
The badge returns one of: operational, degraded, partial-outage, or major-outage with corresponding colors.
API endpoints
Get current status
Returns current status for all services on the page, including active incidents and estimated resolution time.
Get incident history
Returns resolved incidents within the specified window.
Subscribe to updates
Customer impact check
When an incident is detected, Obtrace evaluates which status page services are affected based on service dependency mapping. If the impacted service is listed on a status page, the page updates within 30 seconds.
You can query customer impact programmatically:
Limitations
- Status pages reflect automated incident detection. If your detection rules are too sensitive, the page may show false degradations.
- Custom domain TLS provisioning can take up to 10 minutes on first setup.
- The embed widget adds approximately 8KB (gzipped) to your page load.