Skip to content
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

summaryTrendStats option doesn't affect the k6 REST API results #1253

Open
na-- opened this issue Nov 25, 2019 · 0 comments
Open

summaryTrendStats option doesn't affect the k6 REST API results #1253

na-- opened this issue Nov 25, 2019 · 0 comments
Labels
bug evaluation needed proposal needs to be validated or tested before fully implementing it in k6 lower prio

Comments

@na--
Copy link
Member

na-- commented Nov 25, 2019

Running k6 with custom trend columns like this: k6 run --linger --summary-trend-stats="min,med,avg,count,max,p(85),p(95),p(99),p(99.9),p(99.999)" github.com/loadimpact/k6/samples/thresholds_readme_example.js

And then calling the REST API /v1/metrics method: curl -s 'http://localhost:6565/v1/metrics' | jq '.data[] | select(.id == "group_duration")'

I'd expect to see the percentiles I configured in summaryTrendStats, but instead I see something like this:

{
  "type": "metrics",
  "id": "group_duration",
  "attributes": {
    "type": "trend",
    "contains": "time",
    "tainted": null,
    "sample": {
      "avg": 128.2877491095891,
      "max": 146.327711,
      "med": 127.666555,
      "min": 123.76435,
      "p(90)": 131.6244158,
      "p(95)": 133.2135961
    }
  }
}

Not sure if this is a bug, since after all, the option is supposed to affect the end-of-test summary columns. That said, I expected it to modify the REST API results, and given that there's no other way to configure them, I don't see why it shouldn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug evaluation needed proposal needs to be validated or tested before fully implementing it in k6 lower prio
Projects
None yet
Development

No branches or pull requests

1 participant