-
Notifications
You must be signed in to change notification settings - Fork 238
metrics: Use the correct term for types #2019
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
base: main
Are you sure you want to change the base?
Conversation
I should update the all the previous versions + next. I will do it asap tomorrow. |
0c60062
to
a10b6d8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reminder: Unexpected
@@ -7,7 +7,7 @@ weight: 72 | |||
|
|||
# Rate | |||
|
|||
_Rate_ is an object for representing a custom metric keeping track of the percentage of added values that are non-zero. It is one of the four [custom metrics](https://grafana.com/docs/k6/<K6_VERSION>/javascript-api/k6-metrics). | |||
_Rate_ is an object for representing a custom metric keeping track of the percentage of added values that are non-zero. It is one of the four [metric types](https://grafana.com/docs/k5/<K6_VERSION>/javascript-api/k6-metrics). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are we downgrading k6 to k5 😱
As this is not relevant for the release, I set this back to a draft because it requires additional work. |
What?
In principle k6 has metric types and users can create custom metrics with them. But the two definitions are not strictly the same.
Checklist
npm start
command locally and verified that the changes look good.docs/sources/k6/next
folder of the documentation.docs/sources/k6/v{most_recent_release}
folder of the documentation.docs/sources/k6/next
folder of the documentation.Related PR(s)/Issue(s)