Hi,
Any updates on this old issue. I am having the same issue. Should this issue be logged with datadog ? If yes, where exactly do we log this datadog issue ?
I am seeing the following highlighted K6 metrics (http_req_duration.avg and http_req_failed count in percentage) in teamcity build log -
However , on datadog, it shows different values. Not sure where it is pulling the http_req_failed value in number which is totally unrelated to the percentage number above
k6.http_req_duration.avg → Avg = 59.1s. k6.http_req_failed → Avg = 4.76
I use following docker run command -
K6_STATSD_ENABLE_TAGS=true K6_STATSD_ADDR=cypress-dd-agent:8125 K6_STATSD_PUSH_INTERVAL=10ms k6 run…
I reduced pushinterval to 10 ms after reading this issue - Missing data with statsd output - #6 by mstoykov
However I am stuck as to what else can be done to ensure that K6 build log metrics matches datadog metrics.
All my datadog graphs show a close but different number than K6 build logs.
Since no one is working on this issue, is migrating to grafana a better solution than trying to resolve this datadog issue.
Please guide or fix this issue as it is blocking our usage of K6 and Datadog.