Datadog

Datadog is a comprehensive monitoring and analytics platform that provides real-time insights into application performance, infrastructure health, and security metrics, enabling DevOps teams to optimize system reliability and troubleshoot issues across cloud and on-premises environments.

Power end-to-end data operations for your Datadog API with Nexla. Our bi-directional Datadog connector is purpose-built for Datadog, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Datadog or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Datadog workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Datadog credential, you need to obtain an Organization API Key and an Application Key from your Datadog account. Both keys are required to authenticate with the Datadog API.

To obtain your Organization API Key and Application Key, you need to have a Datadog account with API access enabled. Once you have access to your account, you can generate these keys from your Datadog account settings. The Organization API Key identifies your organization, while the Application Key, in conjunction with your Organization API Key, gives you access to read data from Datadog. Both keys are sent as custom headers (DD-API-KEY and DD-APPLICATION-KEY) for all API requests to the Datadog API. For detailed information about API key setup and authentication, refer to the Datadog API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Organization API Key	Yes	Yes	To use the Datadog API, you will need to provide an Organization API key. See https://docs.datadoghq.com/api/latest/authentication/ for instructions.
Application Key	Yes	Yes	Application keys, in conjunction with your org API key, give you access to read data from Datadog. See https://docs.datadoghq.com/api/latest/authentication/ for instructions.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Datadog

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Datadog Organization API Key in the Organization API Key field. This is the Organization API Key you obtained from your Datadog account settings. The Organization API Key identifies your organization and is sent in the DD-API-KEY header for all API requests to the Datadog API.

   Keep your Organization API Key secure and do not share it publicly. The Organization API Key provides access to your Datadog account and should be treated as sensitive information. The Organization API Key is sent in the DD-API-KEY header for all API requests to the Datadog API. For detailed information about obtaining and managing API keys, see the Datadog API documentation.

4. Enter your Datadog Application Key in the Application Key field. This is the Application Key you obtained from your Datadog account settings. The Application Key, in conjunction with your Organization API Key, gives you access to read data from Datadog. The Application Key is sent in the DD-APPLICATION-KEY header for all API requests to the Datadog API.

   Keep your Application Key secure and do not share it publicly. The Application Key provides access to read data from your Datadog account and should be treated as sensitive information. The Application Key, in conjunction with your Organization API Key, gives you access to read data from Datadog. The Application Key is sent in the DD-APPLICATION-KEY header for all API requests to the Datadog API. For detailed information about obtaining and managing application keys, see the Datadog API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Datadog connector tile, then select the credential that will be used to connect to the Datadog instance, and click Next; or, create a new Datadog credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Datadog endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get your Managed Orgs

This endpoint fetches a list of your managed organizations. Use this endpoint when you need to access organization information, managed organization data, or organization lists from your Datadog account.

• This endpoint automatically retrieves all managed organizations from your Datadog account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to https://api.datadoghq.com/api/v1/org. The endpoint URL is automatically constructed based on the Datadog API base URL.
• The endpoint does not use pagination and returns all managed organizations in a single request.
• The endpoint will return all managed organizations. The response data is extracted from the orgs array in the API response ($.orgs[*]), with each organization record processed individually.

This endpoint returns information about all managed organizations in your Datadog account. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $.orgs[*], which extracts all items from the orgs array in the API response. For detailed information about listing managed organizations, see the Datadog API documentation.

Query Event Stream

This endpoint fetches events that are within a start and end time range. Use this endpoint when you need to access event data, monitoring events, or event streams from your Datadog account for a specific time period. Use the advanced tab for fetching events with other query criteria.

• Enter the start time for events query in the Start Time (Posix Epoch in seconds) field. This must be a valid POSIX time in seconds (Unix timestamp). You can use Nexla macros like {now} for the current time or {now-1} for 24 hours ago. The default value is {now-1} (24 hours before the time of request) if not specified.

• Enter the end time for events query in the End Time (Posix Epoch in seconds) field. This must be a valid POSIX time in seconds (Unix timestamp). You can use Nexla macros like {now} for the current time. The default value is {now} (time of query execution) if not specified.

• The endpoint uses GET requests to https://api.datadoghq.com/api/v1/events?start={'{start}'}&end={'{end}'}&page={'{page}'} where {start} is the Start Time, {end} is the End Time, and {page} is the pagination page number. The endpoint URL is automatically constructed based on the Datadog API base URL and the time range and pagination parameters.
• The endpoint uses incrementing pagination, automatically fetching additional pages as needed. Pagination starts from page 1 and increments by 1 for each subsequent page. Nexla will continue fetching pages until all events in the specified time range are retrieved.
• The endpoint will return all events within the specified start and end time range. The response data is extracted from the events array in the API response ($.events[*]), with each event record processed individually.

Time values must be valid POSIX time in seconds (Unix timestamps). You can use Nexla macros like {now} for the current time or {now-1} for 24 hours ago. The endpoint uses incrementing pagination (iteration.type: paging.incrementing) starting from page 1. The response data path is $.events[*], which extracts all items from the events array in the API response. Use the advanced tab for fetching events with other query criteria beyond the time range. For detailed information about querying the event stream, see the Datadog API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Datadog data sources can also be manually configured to ingest data from any valid Datadog API endpoint, including endpoints not covered by the pre-built templates or requiring chained API calls or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Datadog API endpoints typically follow the pattern https://api.datadoghq.com/api/v1/{endpoint_path} or https://api.datadoghq.com/api/v2/{endpoint_path}. The endpoint requires custom headers for authentication (DD-API-KEY and DD-APPLICATION-KEY), which are handled automatically by your credential configuration. Datadog API responses may use different structures like events arrays, orgs arrays, or root-level objects depending on the endpoint, so the Path to Data field should be set accordingly (for example, $.events[*] or $.orgs[*]).

Once all of the relevant settings have been configured, click the Save button to save your data source configuration. Nexla will now begin ingesting data from the configured endpoint according to the configured schedule and will organize any data that it finds into one or more Nexsets.