Our Gateway API allows users of third-party observability services, like Datadog, to send that data to New Relic.
This feature is currently in beta and at this time only supports DataDog. For questions, contact firstname.lastname@example.org.
With the Gateway API enabled, when data arrives it's copied and sent both to the original endpoint and to New Relic's data transformation service. The transformation service converts the data to a New Relic-supported format and then sends the data to our ingest APIs, making it available for querying and building charts and dashboards.
Requirements for the Gateway API:
- This feature is currently in beta: for details, see our pre-release policy.
- Only supports DataDog:agent 6.x or higher.
Here's an overview of the steps for enabling the Gateway API for DataDog:
For DataDog: Our account representatives will work with you to map your Datadog API keys to New Relic keys.
For each agent configuration file, point the data to
https://gateway.service.newrelic.com. An example for DataDog: in the agent’s
datadog.yamlfile, you’d change these settings:dd_url: https://gateway.service.newrelic.comlogs_config:logs_dd_url: https://gateway.service.newrelic.comuse_compression: trueuse_http: trueapm_config:apm_dd_url: https://gateway.service.newrelic.com
Reboot the agent for each host.
Telemetry data brought in from third-party platforms doesn't map perfectly to our data structure. We will continue to align data structure mapping but currently there are some limitations for that. Here are some important aspects of data transformation:
- Each data type (metrics, logs, traces, events) goes through its relevant ingest API. For restrictions and limits, see those API docs.
- There are no default UI experiences (for example, charts or dashboards) built with this data, but this data can be queried with NRQL and used to create custom charts and dashboards.