---
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


---

# Data mapping form

# Service Observability data mapping form {#ariaid-title1}

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

Field descriptions for the Observability data mapping form. Use this form to map activated services in Service Observability to metrics from your application performance monitoring (APM) instance. Each service can be mapped only once, but can contain exceptions to include all related entities.
{#observability-data-mapping-form__table_jkt_gvj_xdc__entry__2}

| Field | Description |
|-|-|
| Mapping name | Name for the mapping. The name should be descriptive so that users understand where the data is coming from. |
| Services | Service to use for this mapping. Each service can be mapped only once. For version 1.5.0 of Service Observability, services must be activated to be mapped. To activate a service, see [Activate teams and services](https://servicenow-prod.fluidtopics.net/BekT7A59xhh4BRa23PkO8Q "Follow this step only if you are on version 1.5.0 of Service Observability. Assign existing teams to Service Observability so they can view the data returned by the Configuration Management Database (CMDB) on those pages. Activate the services in the CMDB for use in Service Observability."). |
| Default ||
| Find metrics from this source | Existing data connection to use for metrics. To add a connection, see [Connect a Service Observability data source](https://servicenow-prod.fluidtopics.net/r8tDxUIrS533znEw8FX5Aw "Connect Service Observability to an external application performance management (APM) instance. Service Observability displays metrics in the Service Operations Workspace (SOW) from that APM instance."). |
| where source tag key | Tag key that you want to map to the activated service. If you use more than one tag to represent a service, you can create an exception. For example, most tags use `service_name` except for database metrics, which use `service`. |
| source tag value | Value that represents the service name. Values can be strings or a variable that represents fields on the CI for the service. You can use variables on your APM data as the value to map multiple entities at once. For example, if your APM data uses the `$service_name` variable and you enter that as the source tag value, all services using that value are mapped. |
| Exceptions ||
| For entity type | Entity that uses a different key or value than the default. |
| Find metrics from this source | Existing data connection to use for metrics. To add a connection, see [Connect a Service Observability data source](https://servicenow-prod.fluidtopics.net/r8tDxUIrS533znEw8FX5Aw "Connect Service Observability to an external application performance management (APM) instance. Service Observability displays metrics in the Service Operations Workspace (SOW) from that APM instance."). |
| where source tag key | Tag key that you want to map to the activated service for this entity. |
| source tag value | Value that represents the service name. Values can be strings or a variable that represents fields on the CI for the service. |
[ ]

{#observability-data-mapping-form__table_jkt_gvj_xdc}