Services

Overview

A service is a logical grouping that represents a component of your application architecture — such as an API gateway, a payment backend, a database cluster, or a web frontend. By organizing your sensors into services, you gain a structured, high-level view of your system's health.

Services are the foundation for two powerful features:

• Service Dependency Map — a visual graph that shows how your services relate to each other.
• Incident Propagation — automatic detection of cascading failures across dependent services.

You can manage services from Settings → Services in the Onagre dashboard.

Why use services?

Without services, your monitoring is a flat list of individual sensors. As the number of sensors grows, it becomes difficult to understand which part of your system is affected when something breaks.

Services solve this by letting you:

• Group related sensors under a single logical component.
• See health at a glance — each service computes its status from its sensors (Healthy, Degraded, Down, Unknown).
• Model dependencies between services to understand upstream and downstream impact.
• Identify root causes faster when a failure cascades across your architecture.

Managing services

Create a service

1. Navigate to Settings → Services.
2. Click New service.
3. Enter a name (e.g. Payment API) and an optional description.
4. Save.

You can create as many services as your architecture requires.

💡 Default service

Every organization has one default service that cannot be deleted. When creating a new sensor, the default service is pre-selected.

Edit or delete a service

• Click the edit button next to a service to update its name or description.
• Click the delete button to remove a service. The default service cannot be deleted.

Assigning sensors to services

Each sensor belongs to exactly one service. When you create or edit a sensor, select the target service in the General settings section.

Once assigned, the sensor contributes to the service's health status:

Service detail page

Click on a service name to open its detail page. This view provides:

• Health status with sensor statistics (total, up, down).
• Upstream dependencies — services this one depends on.
• Downstream consumers — services that depend on this one.
• Sensor list — all sensors assigned to the service, with their type, status, environment, schedule, and last check time.

From this page, you can navigate directly to related services or individual sensor details.

Summary