Add support for metrics from the DataDog Agent

[dsobolev-nr]

Component(s)

receiver/datadog

Is your feature request related to a problem? Please describe.

Customers of DataDog that wish to use OpenTelemetry on their data encounter a problem with the current receiver as it only supports trace and not metrics or logs.

Describe the solution you'd like

Customers of DataDog should be able to point any agent at an OpenTelemetry collector and process the metrics data emitted.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/datadog: @boostchicken @gouthamve @jpkrohling @MovieStoreGuy

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jpkrohling]

@dsobolev-nr, I'm sure @boostchicken will be happy to review PRs implementing this.

[boostchicken]

Yeah absolutely, I don't know Datadogs format for metrics or logs, It doesn't use the trace agent format, I believe it goes direct to the API like in datadogexporter

[boostchicken]

https://docs.datadoghq.com/api/latest/logs/#send-logs

https://docs.datadoghq.com/api/latest/metrics/#submit-metrics

I believe these are the API's it would need to support

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/datadog: @boostchicken @gouthamve @jpkrohling @MovieStoreGuy

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[mvadu]

https://docs.datadoghq.com/api/latest/logs/#send-logs

https://docs.datadoghq.com/api/latest/metrics/#submit-metrics

I believe these are the API's it would need to support

Those endpoints are more about if you want to send the metrics directly from code to DataDog HQ. But not about how the trace agent (dd-agent.jar for example) itself is sending them to datadog agent. I think this https://docs.datadoghq.com/tracing/metrics/metrics_namespace/ makes more send from trace metrics stand point.

@dsobolev-nr if you original usecase is related to custom metrics generated from your code using DataDog SDK, then it probably uses dogstatds method https://docs.datadoghq.com/metrics/custom_metrics/dogstatsd_metrics_submission/ and we have been successful in replacing the dogstatsd with statsd exporter and translate custom metrics into Prometheus metrics.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/datadog: @boostchicken @gouthamve @jpkrohling @MovieStoreGuy

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[boostchicken]

This a totally different datadog agent, The current receiver has t he Trace Agent API implemented, Metrics I do believe go directly to datadogs SaaS api.

https://docs.datadoghq.com/api/latest/metrics/#submit-metrics

That is the API we need to create receiver for. In theory not a ton of work. there are a lot of other APIs for querying and stuff that we won't since we don't store the data.

@MovieStoreGuy @jpkrohling

If that approach sounds good I could whip something pretty quickly.