> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/3.0/shared-capabilities/application-maps.md).
# Application Maps
Visualize and manage your application dependencies and service relationships in chaos engineering
An application map groups several [services](/resilience-testing/3.0/shared-capabilities/services.md) 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.
{% hint style="info" %}
**NOT PART OF SERVICE ONBOARDING**
Application maps are a separate Insights feature. They are not created by the Resilience Testing service onboarding wizard, and application-level resilience scoring across a map is not available in this release.
{% endhint %}
***
### Before you begin
* [Service discovery](/harness-platform/3.0/harness-platform-resources/service-discovery.md)
* [Automated service onboarding](/resilience-testing/3.0/shared-capabilities/services/service-discovery.md)
* [Services](/resilience-testing/3.0/shared-capabilities/services.md)
* [Create Discovery Agent](/harness-platform/3.0/harness-platform-resources/service-discovery/customize-agent.md#create-discovery-agent)
* [What is Application Map?](/harness-platform/3.0/harness-platform-resources/application-map.md)
***
### 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.
| Column | What it shows |
| ----------------------- | --------------------------------------------------------------------------------------- |
| **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](/harness-platform/3.0/harness-platform-resources/application-map.md#create-application-map) and follow the steps, except, navigate to the **Resilience Testing** module, and select **Project Settings**, and then select **Discovery**.
{% hint style="info" %}
**NOTE**
Alternatively, navigate to **Resilience Testing** -> **Insights** -> **Application Maps** -> **Manage Discovery in Project Settings**. This also leads you to the page in step 2.
{% endhint %}
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**.
{% hint style="info" %}
**NOTE**
* To view chaos-enabled experiment map, navigate to the **Resilience Testing** module and select **Insights** -> **Application Maps**.
* To manually associate the experiment as a part of an application map, specify the tag `applicationmap=` in the experiment.
{% endhint %}
***
### Next Steps
* [Edit Application Map](/harness-platform/3.0/harness-platform-resources/application-map.md#edit-application-map)
* [Delete Application Map](/harness-platform/3.0/harness-platform-resources/application-map.md#delete-application-map)
* [Services](/resilience-testing/3.0/shared-capabilities/services.md): Onboard the services you want to group into a map.
{% @harness-feedback/feedback %}