--- sourceDocument: Zurich IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Connect a data source # Connect a Service Observability data source {#ariaid-title1} * Release version: Zurich * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Connect Service Observability to an external observability system. Service Observability displays metrics in the Service Operations Workspace (SOW) from that observability instance. ## Before you begin You must enter a connection URL and credentials for your observability 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} | Observability 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 | | Zabbix | The connection URL must be the IP on which the Zabbix server is hosted | [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} | Observability 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 SaaS Classic | API | API Tenant Access Token The token must have `entities.read` and `metrics.read` scope permissions. | | Dynatrace SaaS Grail | API | API Platform Token The token must have `storage:metrics.read ` and `storage:bucket.read` scope permissions. | | Dynatrace on-premise | API | * API key. The key must be an environment scoped token. * The name of the MID Server your Dynatrace instance is hosted on {#connect-an-observability-data-source__ul_f3h_fh1_d3c} | | LogicMonitor | API | Access token | | 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 Enterprise | API | Bearer Token | | Splunk Observability | API | Access token | | ThousandEyes | API | API key | | Zabbix | Basic Auth | * Basic Auth credential user name * Basic Auth credential password * The name of the MID Server your Zabbix instance is hosted on. The MID Server must be in an active state. {#connect-an-observability-data-source__ul_vyq_m31_d3c} | [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 observability data is to create a connection to the observability instance. Service Observability supports the following observability vendors: * Amazon CloudWatch * AppDynamics * Cisco ThousandEyes synthetic tests * Datadog * DynatraceSaaS and on-premise (both Classic and Grail environments) * LogicMonitor * Microsoft Azure Monitor * New Relic * Prometheus on-premise * SolarWinds on-premise * Splunk Observability and logs from Splunk Enterprise * Zabbix on-premise {#connect-an-observability-data-source__ul_xdx_mdz_tgc} ## Procedure 1. Navigate to AllService Operations WorkspaceConfigurations, then navigate to Service ObservabilityData sources. 2. Select your observability vendor. 3. On the Add connection form, fill in the fields. You can use an existing HTTP or HTTPs connection and an existing 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://www.servicenow.com/docs/ZrIKyhwIbXlVH6eyBx0ghw "Map your services to the data from a connected external observability vendor instance, and view it in charts for the service."). *[\>]: and then