A note for the community
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
I currently have a ton of metrics being sent by multiple services and developers. Some of those metrics have high tag cardinality that I'd like to limit (things like accidentally adding request_id) while others are valid and should not be limited, like tenant_id.
Attempted Solutions
No alternative solution has been attempted because as far as I know there is no way to persist a cache between transforms or filters.
Proposal
Adding an exclude option to the tag_cardinality_limit transformer will allow users to select specific metric tags to exclude from the limit.
References
No response
Version
0.39.0
A note for the community
Use Cases
I currently have a ton of metrics being sent by multiple services and developers. Some of those metrics have high tag cardinality that I'd like to limit (things like accidentally adding
request_id) while others are valid and should not be limited, liketenant_id.Attempted Solutions
No alternative solution has been attempted because as far as I know there is no way to persist a cache between transforms or filters.
Proposal
Adding an
excludeoption to thetag_cardinality_limittransformer will allow users to select specific metric tags to exclude from the limit.References
No response
Version
0.39.0