Follow the incident across your estate.
Keep the region, cluster and service hierarchy in view while following a specific incident path across dependencies.
Premium Invented demonstration data · Library 1.1.5
How to read this example
- 01
Locate the affected region.
Each coloured facet belongs to a region. Read outward from the control plane through regions and clusters to individual services.
- 02
Follow one explicit path.
The dashed path traces the example incident from authz-cache in Frankfurt through session-api and checkout to billing-ledger in Virginia.
- 03
Inspect the affected service.
Select a node to inspect its severity and connections. Use the topology as context for investigation; a displayed dependency alone does not establish causality.
Try thisFollow authz-cache in Frankfurt through session-api and checkout to billing-ledger in Virginia. Select a node for its relationships and incident context.
Data requirements
- Nodes with stable IDs, hierarchy levels and region or domain membership.
- Edges describing the dependencies you want to show.
- An explicit incident path, plus severity and anomaly metadata where known.
The example configuration shows the data shape, link keys and required modules. Inspect the setup →
Read the chart data
Open the example’s Agent view to read its actual chart.describe() model as text, a table or JSON. In multi-chart examples, choose the view you want to inspect.
The optional describe module is loaded on demand. The website does not calculate its own substitute totals.
Use this configuration in your project
Inspect the configuration, connect your data, and choose the rights that fit your application.