Tracevium Documentation
Everything you need to monitor your APIs, manage incidents, and keep your team informed.
HTTP checks on configurable intervals with uptime tracking.
Capture, store, verify, and replay inbound webhooks.
Auto-detected outages with full lifecycle management.
Public project health pages for your customers.
Alert channels: Slack, PagerDuty, email, and more.
Schedule downtime so alerts stay silent when expected.
Owner, admin, developer, and viewer access levels.
Programmatic access to everything in Tracevium.
Quick start
Get from zero to monitoring in under five minutes:
Create a project
Projects are containers for endpoints, webhooks, and incidents. Go to Projects → New project and give it a name and a key (used in webhook URLs and status page URLs).
Add an endpoint
Inside your project, add an API endpoint with its URL and the check interval you want (30 s, 1 min, 5 min, etc.). Tracevium starts probing immediately.
Configure a notification channel
Go to Notification Channels and connect Slack, PagerDuty, or another channel. Assign it to your project so your team gets paged when something goes wrong.
Invite your team
Go to Members → Invite. Assign roles based on what each person needs to do. Viewers can see dashboards; developers can manage endpoints; admins can manage everything.
Core concepts
Organisation — the top-level account. All billing, members, and projects belong to an organisation. You can be a member of multiple organisations.
Project — a logical grouping of endpoints and webhooks, typically one per service or product. Each project has its own status page and signing secret.
Endpoint — an HTTP URL that Tracevium probes on a schedule. Each check records the status code, response time, and whether it passed or failed.
Incident — auto-created when an endpoint fails consecutively. Resolves automatically on recovery. Learn more →
Webhook event — an inbound HTTP POST stored with full payload and headers. Learn more →