You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From my understanding, currently the extension provides no custom metrics. When I execute a test I get the following output:
I'd like to be able to gather metrics around the latency of requests and the number of requests made during the test. The final goal is to be able to extract information about the latency's p(90), p(95), p(99) and the RPS. Is this on the roadmap of the project? If not, would it be possible to implement such feature?
I'll look into the K6 metrics API and start experimenting with it, but I'd love to hear your thoughts on this.
The text was updated successfully, but these errors were encountered:
I was able to hack something together that looks like this:
I'll probably open a draft PR so we can better discuss the implementation. I think a good addition to that would be to add a metric similar to HTTP's http_req_failed with the option for the user to define how to determine if a request was successful or not, probably an API like HTTP's setResponseCallback.
Hello!
From my understanding, currently the extension provides no custom metrics. When I execute a test I get the following output:
I'd like to be able to gather metrics around the latency of requests and the number of requests made during the test. The final goal is to be able to extract information about the latency's p(90), p(95), p(99) and the RPS. Is this on the roadmap of the project? If not, would it be possible to implement such feature?
I'll look into the K6 metrics API and start experimenting with it, but I'd love to hear your thoughts on this.
The text was updated successfully, but these errors were encountered: