--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Configure Datadog metric pull connector # Configure Datadog metric pull connector {#ariaid-title1} Release version: Australia Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Configure OAuth-based integration between your Datadog instance and ServiceNow Event Management to securely ingest metric from the Datadog Instance. This setup enables authenticated metric delivery using client credentials, maps discovered server CIs, and allows anomaly alerts to create actionable events in ServiceNow through standard webhooks. ## Before you begin Configure the Datadog API Key credential from AllConnections and CredentialsCredentials. For more information on how to configure Datadog API Key credential, see [API key credentials](https://www.servicenow.com/docs/access?context=API-key-credential-form&version=australia&pubname=australia-platform-security&ft:locale=en-US). Ensure you have the application key configured in the Datadog. For more information, see . To use container metrics: First, discover your Docker Container CIs (through Discovery, Cloud Discovery, or Agent Client Collector) so that the container_id field on each cmdb_ci_docker_container record is populated. The shipped Datadog Metrics Container Binding event rule matches container metric events to these CIs based on container_id. Datadog reports the container_id as the container's short ID (the first 12 characters of the Docker container ID), which is what Discovery stores on the CI. Once the CIs are discovered, enable the Enable container metrics advanced setting (set it to true). Role required: evt_mgmt_admin ## About this task The Datadog connector can collect Docker container metrics and bind them to Docker Container CIs (cmdb_ci_docker_container). This capability is off by default and is enabled through the Enable container metrics advanced setting. ## Procedure 1. Navigate to WorkspacesService Operations Workspace. 2. From the navigation pane, select the AIOps configuration center icon ![ITOM AIOps configuration center icon](). The ITOM AIOps configuration center page appears. The configuration center is a centralized workspace. Use it to configure and manage AIOps features from a single place. 3. On the ITOM AIOps configuration center page, under the SetupIntegrations section, select Manage Installed integrations. 4. In the Browse Integrations tab, select the All integrations drop-down list and select MetricsPull. Only metric pull connector tiles are displayed. 5. Select the Datadog Metrics connector tile. 6. In the Provide details section, enter the following information and select Next. * In the Name field, enter a unique name for the connector type. * In the Data source field, the external source for retrieving metrics is auto-populated based on the tile type you select. In this case, select Datadog. * In the Description field, enter brief information about this connector. {#configure-datadog-metric-pull-connector__ul_rtp_1jd_kfc} 7. In the Set data retrieval method section, enter the following information: * In the Hostname/Host IP field, enter the IP address that is related to the Datadog server. * From the Credentials drop-down list, select the valid credentials to access the metrics source host. Select the credential. * In the Metric collection schedule (in seconds) field, enter the time interval (in seconds) at which the connector retrieves metrics from the source host. The default value is 60 seconds. * In the MID Server field, select a MID Server that collects metric data from external tools and securely sends it to ServiceNow. If none are available, ensure one is installed, running, and has the required capabilities. If none are available, ensure one is installed, running, and has the required capabilities. For example, the Metric Intelligence Context must be running on the same MID Server that you are configuring. Note: You can select multiple MID Server. The system randomly assigns one as the primary and uses the others as backups. * in the Application key field, enter the application key that is associated with the user account. {#configure-datadog-metric-pull-connector__ul_drv_mjd_kfc} 8. **Optional:** If you want to customize configurations to meet specific requirements, select Advanced settings and fill in the form. For more information on fields, see [Datadog advanced settings fields](https://www.servicenow.com/docs/qfm_TvOODnIQgXuYC~i4Rw "Populate the Datadog advanced settings fields to define API paths, batching limits, host filters, sync duration, connection details, and debugging options. These values control how the pull connector retrieves and processes metrics and host data from Datadog, ensuring the connector runs with the desired scope and behavior."). 9. **Optional:** Test the connector before activating it by selecting Test and Save. 10. To save the connector, select Save. 11. To activate the pull connector, select Activate. The metric pull connector is activated and its tile is displayed in the Installed Integrations tab. When you open the tile, you can find the Overview, Details, and Data retrieval method tabs. The Overview tab allows you to verify that the connector is running and collecting data. It also offers options to improve system settings, such as refining alert definitions or enhancing binding configurations. The Details tab allows you to update the connector's general information (such as name or description) and displays any errors encountered during its operation. The Data Retrieval Method tab contains the connector settings (such as host, port, and credentials) and may provide additional details for issues like MID Server errors. {#configure-datadog-metric-pull-connector__steps_srm_zfk_5wb} *[\>]: and then