-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
VictoriaMetrics Datadog APM/Trace Agent URL integration #6278
Labels
question
The question issue
Comments
hey @michalgoldys |
Hey @AndrewChubatiuk thanks for the reply. Could you reveal any potential assumptions when traces are planned to be supported? |
Suppose it's a mid/long-term goal, but anyway will let you know in case of any updates |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your question request related to a specific component?
No response
Describe the question in detail
Hey there!
As described here:
https://docs.victoriametrics.com/single-server-victoriametrics/#how-to-send-data-from-datadog-agent
https://docs.victoriametrics.com/url-examples/#datadog
VictoriaMetrics supports Datadog Agent metrics collection for specific endpoints.
I'm wondering, if VictoriaMetrics supports, or will support collecting data from Datadog Trace Agents.
You could easily achieve this by changing the proper environment variable - which I did:
https://github.com/DataDog/datadog-agent/blob/878600ef7a55c5ef0efb41ed0915f020cf7e3bd0/pkg/config/config_template.yaml#L1242
I've tried to tide up the Datadog Trace Agent data forwarding to the VictoriaMetrics URL. I changed the
apm_dd_url
to match my VictoriaMetrics setup, but unfortunately looks like the given path for VictoriaMetrics seems to be unknown:It is more related to Application Performance Monitoring (https://docs.datadoghq.com/tracing/) instead of typical "metrics".
I'm not sure if such a solution is supported.
Do I do something wrong, or just Traces/APM is not supported?
I am using
victoria-metrics-single
helm chart in version0.9.17
with app running onimage v1.99.0
Troubleshooting docs
The text was updated successfully, but these errors were encountered: