-
Notifications
You must be signed in to change notification settings - Fork 72
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
Filtering metrics by tags #5
Comments
@yorugac is this feature required on the output side? I think the output could just rely on the SystemTags provided by k6. If the user wants to reduce the number of tags delivered s/he can just disable some of them with the option. WDYT? |
I'd say this feature is needed for outputs in general and probably should be part of the core 😅 This issue is not about system tags but about more flexible configuration in general, including custom tags. E.g. Prometheus allows quite a versatile configuration for which metrics and labels to keep and which to discard. But that's configuration for scraping, remote write endpoint doesn't have that, AFAIK. Plus, the issue of slow metrics processing from k6 side has been imposing limits on how much can be processed so filtering seemed like a good addition. That's how this issue appeared initially. Now that I look at it, it can be read as a duplicate for grafana/k6#1321. If so, then it makes sense to close this one: this feature request is more fitting to k6 core anyway. Just to be clear, I consider this a valid feature request regardless of metrics refactoring: as a user, I don't always want to have all metrics stored and system tags option is insufficient.
For sure. These were really just temporary options until something better appears. |
Correction: remote write endpoint can probably rely on |
why is |
To avoid quickly overshooting server side limits, it would be good to have configurable option on how many metrics and how many labels are sent via configuration and perhaps, which ones are sent in the first place.
Partially related k6 issue
The text was updated successfully, but these errors were encountered: