Application Maps
Visualize and manage your application dependencies and service relationships in chaos engineering
An application map groups several services into one logical application so you can visualize related targets together.
A service represents a single target. An application map represents the thing your users actually depend on, which is usually several services working together.
Before you begin
Review your application maps
Go to Resilience Testing → Insights → Application Maps to open the list. Each row names the map and the infrastructure it belongs to.
Application map
The map name, with the infrastructure it was built from beneath it.
Services
How many services the map groups.
Experiments
How many chaos experiments target the map.
Avg resilience
The average resilience score across the map. A map with no completed runs shows a dash.
Resilience coverage
How much of the map your experiments actually exercise.
Last chaos activity
The most recent experiment run against the map, or No executions yet.
A map with services but no experiments is grouped but untested, and a map with experiments but low coverage is only partly tested. Both read as gaps rather than results.
Create Application Map
Go to create an application map and follow the steps, except, navigate to the Resilience Testing module, and select Project Settings, and then select Discovery.
In the step where you select one or more discovered services, choose a specific service on which you want to inject chaos, and click Next.

Next Steps
Services: Onboard the services you want to group into a map.
Last updated
Was this helpful?

