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


---

# Connect a data source

# Connect a Service Observability data source {#ariaid-title1}

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

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.

## Before you begin

You must enter a connection URL and credentials for your APM vendor. You can either use an existing connection or create one. Note the following for specific vendors:{#connect-an-observability-data-source__table_i4m_bwf_yfc__entry__2}

| APM Vendor | Connection information |
|-|-|
| AWS | The connection URL must be specific to the region to be monitored, for example, `https://monitoring.us-east-2.amazonaws.com`. |
| Azure | The connection URL should be `https://management.azure.com`. |
| Splunk Observability | The connection URL must include the Realm, for example, https://stream.\[REALM\].signalfx.com |
[Table 1. Vendor-specific connection information]

{#connect-an-observability-data-source__table_i4m_bwf_yfc}

If you're using existing credentials, you need the credential name. If you're creating credentials, collect the following information.
{#connect-an-observability-data-source__table_kfv_f5t_rfc__entry__3}

| APM vendor | Credential type | Information needed |
|-|-|-|
| AppDynamics | OAuth 2.0 | * OAuth Client ID * OAuth Client secret * OAuth token URL * AppDynamics account name {#connect-an-observability-data-source__ul_pps_l2z_tgc} |
| Azure | OAuth 2.0 | * OAuth Client ID * OAuth Client secret * OAuth token URL * Subscription ID {#connect-an-observability-data-source__ul_igp_p5t_rfc} |
| AWS | AWS credentials | * Access key * Secret key {#connect-an-observability-data-source__ul_tsv_z5t_rfc} If the user associated with this key is restricted to specific permissions, they must include the following, scoped to all resources: * `cloudwatch:Describe` scoped to all resources * `cloudwatch:Get` scoped to all resources * `cloudwatch:List` scoped to all resources * `cloudtrail:LookupEvents` * `tag:GetResources` * `tag:GetTagKeys` * `tag:GetTagValues` * `apigateway:Get` {#connect-an-observability-data-source__ul_qyb_x5f_yfc} |
| Datadog | API | * API key * Application key {#connect-an-observability-data-source__ul_nsn_t5t_rfc} If an application key is restricted to a specific scope, those scopes are required for the following endpoints: * https://api.datadoghq.com/api/v2/catalog/entity * https://api.datadoghq.com/api/v1/hosts * https://api.datadoghq.com/api/v1/query * https://api.datadoghq.com/api/v2/query/timeseries {#connect-an-observability-data-source__ul_cry_gz3_2fc} |
| Dynatrace | API | API key The API key must have `Read entities` and `Read metrics` scope permissions. |
| New Relic | API | * Account ID * API key {#connect-an-observability-data-source__ul_u4k_x5t_rfc} |
| Prometheus (on-premise) | Basic Auth | * Basic Auth credential user name * Basic Auth credential password * The name of the MID Server your Prometheus instance is hosted on {#connect-an-observability-data-source__ul_onq_f2z_tgc} |
| SolarWinds | Basic Auth | * Basic Auth credential user name * Basic Auth credential password * The name of the MID Server your SolarWinds instance is hosted on {#connect-an-observability-data-source__ul_o4s_cvt_rfc} |
| Splunk Observability | API | Access token |
[Table 2. Vendor-specific credential requirements]

{#connect-an-observability-data-source__table_kfv_f5t_rfc}

Role required: sn_sow_svcobs.admin

## About this task

The first step to ingesting APM data is to create a connection to the APM instance.  
Service Observability supports the following APM vendors:

* Amazon CloudWatch
* AppDynamics
* Datadog
* Dynatrace
* Microsoft Azure Monitor
* New Relic
* Prometheus (on-premise)
* SolarWinds on-premise
* Splunk Observability
{#connect-an-observability-data-source__ul_xdx_mdz_tgc}

## Procedure

1. Navigate based on your version of Service Observability.
   * Version 1.5.0: Navigate to AllService Operations WorkspaceConfigurations, then navigate to Service Observability ManagementManage ObservabilityData sources
   * Version 1.6 or later: Navigate to AllService Operations WorkspaceConfigurations, then navigate to Service ObservabilityData sources.
   {#connect-an-observability-data-source__choices_unc_bkc_q2c}
2. Select your APM vendor.
3. On the Add connection form, fill in the fields.  
   You can use an existing HTTP or HTTPs connection and an existing API key credential or create one.
4. Select Save.

## Result

A new connection appears in the list of observability data sources. You use this connection when you create a data mapping.

## What to do next

Map your connection to the services that you want to monitor in Service Observability. See [Create and manage data mappings](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.").

*[\>]: and then