Skip to content
Docs

Service Map

On this page
  1. What it shows
  2. Explore it
  3. Use it during an incident
  4. Edit dependencies on the map
  5. Elsewhere in Onagre

The Service Map draws your whole architecture as Onagre knows it: every service, the dependencies between them, and the health of each one. During an incident, it answers the question a list cannot: what else does this failure reach?

Open it from Monitoring → Service map.

Service dependency map: 15 services on three levels joined by dependency arrows; Developer Docs, Mobile Backend and Notifications are degraded (orange), the others healthy (green).
The whole architecture on one map: color shows health, arrows show who depends on whom.

What it shows#

  • Nodes are services. Each shows its name, its number of sensors and its health — green Healthy, orange Degraded, red Down, grey Unknown.
  • Arrows are dependencies. An arrow from Mobile Backend to Notifications means Mobile Backend depends on Notifications.
  • The health shown includes propagation: a service that depends on a failing service is shown as degraded even when its own sensors are fine.

The map comes from what you declared: the services you created, the sensors you placed in them, the dependencies you added. Onagre does not discover dependencies by itself, so a missing arrow means a dependency nobody declared.

Explore it#

Scroll to zoom, click a service for its details, toggle Propagation, and Fit view to see everything again.
  • Drag the background to move around; scroll to zoom; Fit view brings everything back on screen.
  • Click a service to open its details: health, Total sensors, Sensors up, Sensors down, the services it Depends on and that it is Used by, and View service details. Its links are highlighted.
  • Double-click a service to open its page.
  • Propagation highlights the failing services and the ones they impact — see Incident propagation.
Service map zoomed on Notifications, selected: its node details show a degraded health, the share of resources up and down, the services it depends on and the services that use it.
Clicking a service shows its health and dependencies without leaving the map.

Use it during an incident#

  1. Open the map: the failing service is red or orange.
  2. Turn on Propagation: the services impacted through dependencies appear with a dashed orange border, and the paths are drawn in orange.
  3. Click the failing service to see its sensors up and down, then View service details to reach the failing sensor and its incident.

Edit dependencies on the map#

Link mode (hidden for Viewers) lets you draw dependencies:

  1. Click Link mode.
  2. Drag from the service that depends to the service it depends on; an arrow follows the pointer.
  3. Release on the target: the dependency is created. Press Esc to cancel a drag.
  4. Click Link mode again to leave the mode.

To delete a dependency, click its arrow and confirm. Dependencies can also be managed from Configuration → Services — see Services.

Elsewhere in Onagre#

Each sensor's page has a Service dependencies card: a small map of the sensor's service and its direct neighbours. It is the quickest way to see what a failing sensor may affect.