-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[exporter/datadog] Add support for Live Processes metrics upload to Datadog #27858
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Thanks for reaching out. This is not supported today, please reach out to our support team so we can track this request. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/datadog
Is your feature request related to a problem? Please describe.
Currently
datadogexporter
supports only sending Metrics, Traces, Logs and HostMetadata onto Datadog SaaS (at least judging by configuration options):Describe the solution you'd like
We'd like to have the ability to send Process level metrics we're scrating with the
hostmetrics
receiver onto Datadog and have them appear on Live Processes menu.Judging by
datadog-process-agent
code, processes metrics are expected to arrive at a different Endpoint rather then Metrics: https://github.com/DataDog/datadog-agent/blob/45a28e222a96fb99954eaa84e3cff52058d7b65f/comp/forwarder/defaultforwarder/endpoints/endpoints.go#L37And probably with the different
data_type
rather than "metric".Describe alternatives you've considered
To replicate whatever the Datadog's own Process Agent is doing and how it's formatting data is arguably the best option here.
Additional context
No response
The text was updated successfully, but these errors were encountered: