-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
K6 does not send metrics like k6.http_req_duration.avg to datadog statsd #2776
Comments
We have the same issue in our organisation, any update with the bug? |
Per @olegbespalov and @javaducky, this issue should probably be part of the StatsD project. Feel free to transfer it here: |
Closing in favor of LeonAdato/xk6-output-statsd#25 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brief summary
I am using the K6 datadog integration as mentioned here -
https://k6.io/docs/results-visualization/datadog/
I am using docker container to send metrics to datadog from K6 run through teamcity.
The issue is -
k6.http_req_duration.avg
in datadog UI is close to, but never the same as K6 build log. K6 is not sending certain metrics to Datadog.The details of the issue logged on K6 community website can be found here - https://community.k6.io/t/http-req-duration-wrong-datadog/440/8
see my datadog config below
I opened a ticket with datadog team here - https://help.datadoghq.com/hc/en-us/requests/954788
However, datadog team told me that this is a K6 issue where it is not sending certain metrics for example -
k6.http_req_duration.avg:13930.0 in milliseconds
. Here is a snapshot from their response.Please fix this as it does not seem to be datadog agent issue.
k6 version
~0.37.0
OS
Linux
Docker version and image (if applicable)
No response
Steps to reproduce the problem
Run K6 tests using docker and send data to datadog using statsd agent. Compare metrics like k6.http_req_duration.avg in k6 build log and datadog UI timeseries graph
Expected behaviour
The value of the metric should be the same.
Actual behaviour
The values are close but never the same.
The text was updated successfully, but these errors were encountered: