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

Filtering metrics by tags #5

Open
yorugac opened this issue Oct 29, 2021 · 4 comments
Open

Filtering metrics by tags #5

yorugac opened this issue Oct 29, 2021 · 4 comments
Labels
enhancement New feature or request evaluation needed

Comments

@yorugac
Copy link
Collaborator

yorugac commented Oct 29, 2021

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

@yorugac yorugac added enhancement New feature or request evaluation needed labels Dec 23, 2021
@codebien
Copy link
Contributor

codebien commented Sep 1, 2022

@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.
For the same reason, I think we should remove these options from the configuration.

WDYT?

@yorugac
Copy link
Collaborator Author

yorugac commented Sep 2, 2022

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.

I think we should remove these options from the configuration.

For sure. These were really just temporary options until something better appears.

@yorugac
Copy link
Collaborator Author

yorugac commented Sep 2, 2022

remote write endpoint doesn't have that, AFAIK

Correction: remote write endpoint can probably rely on metric_relabel_configs option to filter metrics received from k6. But that'd be on Prometheus' side, so after metrics were already sent by k6 but before they are stored. And this option may not be present for other remote write outputs. Still, better than nothing.

@codebien codebien mentioned this issue Oct 21, 2022
@smazurov
Copy link

why is systemTags insufficient for basic pairing down of whats sent?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request evaluation needed
Projects
None yet
Development

No branches or pull requests

3 participants