Emit the value of the threshold-metric at the end of the test.

[sniku]

At the end of the k6 run -o cloud test, k6 should send both the result of the threshold and the value of the metric the threshold is using.

Environment

• k6 version: 0.31.1
• k6 run -o cloud test.

Actual Behavior

At the end of the test, k6 sends the result of the threshold (true or false) but does not send the value of the metric itself. k6 currently sends a structure similar to this

{
  "result_status": 0,
  "run_status": 3,
  "thresholds": {
    "check_failure_rate": {
      "rate<0.01": false,
      "rate<=0.05": false
    },
    "http_req_duration{staticAsset:yes}": {
      "p(99)<250": false
    }
  }
}

Expected Behavior

k6 should send both the result of the threshold and the value of the metric the threshold is using. The above structure should look similar to this

{
   "result_status":0,
   "run_status":3,
   "thresholds":{
      "check_failure_rate":{
         "rate<0.01":{
            "result":false,
            "value":0.01
         },
         "rate<=0.05":{
            "result":false,
            "value":0.01
         }
      },
      "http_req_duration{staticAsset:yes}":{
         "p(99)<250":{
            "result":false,
            "value":219.54
         }
      }
   }
}

Steps to Reproduce the Problem

1. Run a k6 run -o cloud script.js test
2. View the Thresholds tab. The value is missing.
   

Dependencies

This issue is most likely blocked by #1443 and #961 because k6 currently doesn't know the threshold metric value since the threshold is evaluated in its own js runtime.
#1832 would help but is not a hard blocker (?).

[mkerollos]

Are there any known workarounds to this issue?

[na--]

No, sorry 😞 I see we've basically cleared all of the blockers for this issue though! So, no promises, but there is a good chance that we will prioritize fixing it in the near future 🤞

[ichepurin]

Hello @na--, was there a fix for this?

[joanlopez]

Hello @na--, was there a fix for this?

Hello @ichepurin,

We're precisely right now discussing a new format, which will contain more test run details including the value, which among other things will help to fix this issue. So, I'm sorry, but I cannot give you a estimate delivery for the fix, but I can happily say finally we're actively working on it. I hope the fix will be there sooner rather than later.

Thanks! 🙇🏻

cc/ @oleiade

Side note: yes, the issue is still reproducible.

[joanlopez]

Closing, as looks like this is no longer an issue (see the screenshot below)

If you find any concrete example that still fails, please let us now.

[ichepurin]

Hi @joanlopez, is there a specific setting I need to set to make these values appear? Still not visible for me.