To create a service, include the
name
of the service and the team_id
it belongs to in the request body. This association ensures that each team is responsible for monitoring and responding to events tied to its own services.Real-world use cases:
- Team-specific service tracking — Allow different teams to independently monitor their own microservices, apps, or integrations.
- Structured growth — As your system scales, teams can register new services under their scope to maintain separation of responsibilities.
- Improved alert ownership — Alerts and incidents triggered from the service can be routed to the right team based on the team_id assignment.
After a service is created, it can be connected to uptime monitors, incident workflows, and team-based notification channels for complete operational visibility.