---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# APM vendor entity mappings

# APM vendor entity mappings for Service Observability {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of APM Vendor Entity Mappings for Service Observability

This document explains how Service Observability integrates with various Application Performance Management (APM) vendors by mapping service, host, and database entities to corresponding resources.
This mapping enables the display of metrics from APM vendors on Observability dashboards based on user-defined mapping rules.
Show full answer Show less  

## Key Features

* **Entity Mapping by Vendor:** Service Observability supports multiple APM vendors, including Amazon CloudWatch, AppDynamics, Azure, Datadog, Dynatrace, New Relic, Prometheus, and Splunk.
* **Resource Retrieval:** Each vendor utilizes specific APIs to retrieve resources, ensuring effective mapping and filtering of entities.
* **Custom Mappings:** Users can create mappings for services lacking metadata, allowing for flexible customization of the integration.
* **Dashboard Templates:** Default dashboard templates are provided, utilizing key metrics for visualizing requests, errors, and latency.

## Key Outcomes

By implementing these mappings, ServiceNow customers can:

* Gain visibility into the performance of services, hosts, and databases across various APM tools.
* Utilize the Observability dashboards to monitor critical metrics and troubleshoot issues effectively.
* Customize dashboard templates to better fit their specific monitoring needs and service configurations.
* Ensure that all relevant APM data is accessible, enhancing operational awareness and response capabilities.  
Understand how Service Observability maps service, host, and database entities to your Application Performance Management (APM) vendor resources.

Service Observability displays metrics from your APM vendor for services, hosts, and databases on the Observability dashboards based on the key:value pairs in the [mapping rules you create](https://servicenow-prod.fluidtopics.net/5bFq1kfuXECPkqiIoQjsqA "Map your services to the data from a connected external application performance management (APM) instance, and view it in charts for the service.") during configuration. Service Observability sends a request to the APM vendor using that mapping as a filter to find related entities. Any additional filtering needed to find the entities is noted in the following sections.

## Amazon CloudWatch entity mapping {#apm-vendor-entity-mappings__section_zzt_3ff_yfc}

Resources are returned using the AWS `GetResources` API.
{#apm-vendor-entity-mappings__table_stx_hq2_yfc__entry__3}

| Service Observability entity category | Service Observability entity dashboard | AWS resource |
|-|-|-|
| Application | API Gateway - HTTP | API Gateway HTTP APIs |
|   | API Gateway - REST | API Gateway REST APIs |
|   | ELB | ELB application load balancers |
|   | Lambda | Lambda functions |
| Compute | Host | EC2 instances |
| Databases | RDS | RDS database instances |
[ ]

{#apm-vendor-entity-mappings__table_stx_hq2_yfc}

## AppDynamics entity mapping {#apm-vendor-entity-mappings__section_tc5_hnv_wgc}

Resources are returned using the value of the `entityName` property.
{#apm-vendor-entity-mappings__table_d4b_zpv_wgc__entry__3}

| Service Observability entity category | Service Observability entity dashboard | AppDynamics resource |
|-|-|-|
| Application | Service | AppDynamics applications returned by the `/controller/rest/applications/` API |
| Compute | Host | Server nodes for applications returned by the `/controller/sim/v2/user/machines/keys/` API |
| Databases | MySQL | MySQL database instances returned by the `/controller/rest/databases/collectors/` |
|   | PostgreSQL | MySQL database instances returned by the `/controller/rest/databases/collectors/` |
[ ]

{#apm-vendor-entity-mappings__table_d4b_zpv_wgc}

## Azure entity mapping {#apm-vendor-entity-mappings__section_rzg_mff_yfc}

Resources are returned using the Azure `ResourceGraph` API.
{#apm-vendor-entity-mappings__table_wzg_sff_yfc__entry__3}

| Service Observability entity category | Service Observability entity dashboard | Azure resource |
|-|-|-|
| Application | Service | * `Microsoft.Compute/cloudServices ` * `Microsoft.Web/sites ` |
| Compute | Host | `Microsoft.Compute/virtualMachines ` |
| Databases | MySQL | * `Microsoft.DBforMySQL/servers ` * `Microsoft.DBforMySQL/fle`++xibleServers++` ` {#apm-vendor-entity-mappings__ul_urb_dlf_yfc} |
|   | PostgreSQL | * ++Microsoft.DBforPostgreSQL/servers++` ` * `Microsoft.DBforPostgreSQL/flexibleServers ` {#apm-vendor-entity-mappings__ul_lxg_flf_yfc} |
[ ]

{#apm-vendor-entity-mappings__table_wzg_sff_yfc}

## Datadog entity mapping {#apm-vendor-entity-mappings__section_ez5_sff_yfc}

{#apm-vendor-entity-mappings__table_cnw_jkf_yfc__entry__3}

| Service Observability entity category | Service Observability entity dashboard | Datadog resource |
|-|-|-|
| Application | Service | Entities returned from the Software Catalog: List Entities API |
| Compute | Host | Hosts returned from the Hosts: List Hosts API |
| Databases | MySQL | Databases returned by filtering the `mysql.net.max_connections` metric, filtered by the provided key:value pair in the data mapping. Note: If your databases don't emit this metric, they aren't mapped. |
|   | PostgreSQL | Databases returned by filtering the `postgresql.connections` metric, filtered by the provided key:value pair in the data mapping. Note: If your databases don't emit this metric, they aren't mapped. |
[ ]

{#apm-vendor-entity-mappings__table_cnw_jkf_yfc}  
Items of note:

* Service entities: The `Software Catalog list entities` API only returns data for services that include metadata. If you want to map services that don't include metadata, you must create a mapping using `service` as the tag and the name of the service as the value.  
  For example, say you have a service named `internet-banking-4` that you want to use in a mapping and it doesn't contain metadata. You set up the mapping as shown in this screenshot.Figure 1. Datadog mapping if no metadata is present
* Default dashboard templates: The Requests, Errors, and Latency charts on the Overview and Observability dashboard templates are created using the Datadog `trace.http.request` trace metric. If a service isn't emitting that metric, no data is found. You can customize the template to use a different trace metric query. See [Customize Service Observability dashboard templates](https://servicenow-prod.fluidtopics.net/Er7WM1Kj0dsqKF4aiScVsQ "You can customize the Service Observability dashboards on both the Overview and Observability tabs of the Service Details page. You can change or add metrics and related data to fit your business needs.") for more information.
{#apm-vendor-entity-mappings__ul_jnq_xnf_yfc}

## Dynatrace entity mapping {#apm-vendor-entity-mappings__section_dkd_xff_yfc}

{#apm-vendor-entity-mappings__table_swf_kkf_yfc__entry__3}

| Service Observability entity category | Service Observability entity dashboard | Dynatrace resource |
|-|-|-|
| Application | Service | Services |
| Compute | Host | Hosts |
| Databases | MySQL | MySQL database instances |
|   | PostgreSQL | PostgreSQL database instances |
[ ]

{#apm-vendor-entity-mappings__table_swf_kkf_yfc}

## New Relic entity mapping {#apm-vendor-entity-mappings__section_odk_qgf_yfc}

{#apm-vendor-entity-mappings__table_lfm_kkf_yfc__entry__3}

| Service Observability entity category | Service Observability entity dashboard | New Relic resource |
|-|-|-|
| Application | Service | APM application services |
| Compute | Host | Hosts |
| Databases | MySQL | MySQL database instances |
|   | PostgreSQL | PostgreSQL database instances |
[ ]

{#apm-vendor-entity-mappings__table_lfm_kkf_yfc}

## Prometheus entity mapping {#apm-vendor-entity-mappings__section_byf_3rp_zgc}

{#apm-vendor-entity-mappings__table_cyf_3rp_zgc__entry__3}

| Service Observability entity category | Service Observability entity dashboard | Prometheus resource |
|-|-|-|
| Application | Service | Applications |
| Compute | Host | Server nodes for applications |
| Databases | MySQL | MySQL database instances |
|   | PostgreSQL | PostgreSQL database instances |
[ ]

{#apm-vendor-entity-mappings__table_cyf_3rp_zgc}

## SolarWinds entity mapping {#apm-vendor-entity-mappings__section_mkf_5gf_yfc}

{#apm-vendor-entity-mappings__table_tvq_kkf_yfc__entry__3}

| Service Observability entity category | Service Observability entity dashboard | SolarWinds resource |
|-|-|-|
| Application | Service | APM application services |
| Compute | Host | Hosts |
[ ]

{#apm-vendor-entity-mappings__table_tvq_kkf_yfc}

## Splunk entity mapping {#apm-vendor-entity-mappings__section_xlw_wgf_yfc}

Resources are returned using the Splunk Metric time series Metadata API. Service Observability searches for matching key:value pairs in custom properties and then falls back to searching dimensions.

The returned payload is then filtered by the presence of a specific metric in the metadata that corresponds with an entity type.
{#apm-vendor-entity-mappings__table_x1w_kkf_yfc__entry__4}

| Service Observability entity category | Service Observability entity dashboard | Splunk Property or dimension | Splunk metric used for filtering |
|-|-|-|-|
| Application | Service | * Property: `sf_service` * Dimension fallback: `service.name` {#apm-vendor-entity-mappings__ul_rfv_dqf_yfc} | `sf_metric:service.request` |
| Compute | Host | * Property: `host.name` * Dimension fallback: `host.id` {#apm-vendor-entity-mappings__ul_w3b_jqf_yfc} | `sf_metric:disk.summary_utilization` |
| Databases | MySQL | * Property: `mysql.instance.name` * Dimension fallback: `mysql.instance.endpoint` {#apm-vendor-entity-mappings__ul_kcg_jqf_yfc} | `sf_metric:mysql.threads` |
|   | PostgreSQL | Not supported |   |
[ ]

{#apm-vendor-entity-mappings__table_x1w_kkf_yfc}