Data & decisions · focused workspace

Service Dependency Impact Map

Trace direct and transitive dependencies in a service inventory and compare the potential blast radius of each failure.

Selected failure impactCompare scenariosCSV & printable report

Make the next step clearer

Open CSV / project

Preparing the worked example…

Make it yours

Settings & assumptions

Services

Your result, explained

02 / RESULTS

Read the result in context

A dependency is treated as mandatory. DAG only: cycles and unknown IDs are rejected. Attached user counts are summed without deduplication; this is a topology scenario, not a health monitor.

How to use Service Dependency Impact Map

Explore the worked example. Model database, login, shop, support and landing services, then trace the consequences of one failed service.
Replace the services with your own entries. Set failed service id.
Choose “Trace failure impact”. Review selected failure impact and all failure scenarios, then compare the visual overview with the detailed tables.
Capture alternative scenarios, download a reusable project and export the selected table or a report when you are ready.

A starting point

Model database, login, shop, support and landing services, then trace the consequences of one failed service. The example is illustrative and can be replaced.

Know what you are comparing

Are attached users deduplicated across services?

No. The result sums entered service-attached counts, which may overlap. Treat it as an impact indicator, not a unique-user outage measurement.

Files, privacy & saving

Calculations run locally in a browser worker. Input CSV files use the column names in the downloadable template and keep your current settings. Projects restore inputs and up to four scenarios. Imports are limited to 1 MiB and 100 entries. There is no automatic saving. Public pages include advertising and optional analytics; see our privacy policy.

CSV exports contain the entire selected table. JSON and printable HTML reports include all result tables; open the report and use your browser’s Print command for PDF.

Using Service Dependency Impact Map

Trace direct and transitive dependencies in a service inventory and compare the potential blast radius of each failure.

Explore the worked example. Model database, login, shop, support and landing services, then trace the consequences of one failed service.
Replace the services with your own entries. Set failed service id.
Choose “Trace failure impact”. Review selected failure impact and all failure scenarios, then compare the visual overview with the detailed tables.
Capture alternative scenarios, download a reusable project and export the selected table or a report when you are ready.

Example

Model database, login, shop, support and landing services, then trace the consequences of one failed service.

Questions & answers

Are attached users deduplicated across services?

No. The result sums entered service-attached counts, which may overlap. Treat it as an impact indicator, not a unique-user outage measurement.

Can I compare and save alternative plans?

Yes. Capture up to four calculated scenarios, restore their inputs and save them in a project JSON file. There is no automatic saving.

How do I bring in my own entries?

Download the CSV template, retain its column names and replace the example rows. Imports are limited to 100 entries and 1 MiB. A saved project also restores settings.

What should I check before using the result?

A dependency is treated as mandatory. DAG only: cycles and unknown IDs are rejected. Attached user counts are summed without deduplication; this is a topology scenario, not a health monitor.