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

otel2influx: Support field for gauge metric #310

Open
Code-Hex opened this issue Jul 9, 2024 · 0 comments
Open

otel2influx: Support field for gauge metric #310

Code-Hex opened this issue Jul 9, 2024 · 0 comments

Comments

@Code-Hex
Copy link

Code-Hex commented Jul 9, 2024

Thank you for the great library. We are using through OpenTelemetry Collector.

We are using a cloud plan and are only sending one gauge metric and now the cardinality is so high that we are using the full plan. Upon investigation, it appears to be due to the creation of lots of tags.

Since most of them are indeed not treated as search filters (for dashboard rendering purposes), we thought it would be nice to be able to send them as fields to improve the situation.

We are using MetricsSchemaTelegrafPrometheusV2 and are sending key values using Resource.attributes. I have consulted the documentation and it seems that it only supports treating them as tags.

As a suggestion, I was wondering if it would be possible to modify the logic to treat a key as a field if its prefix is "field_", for example, while maintaining backward compatibility.

We would appreciate it if you could support treating some of them as fields.

@Code-Hex Code-Hex changed the title Support field for gauge metric otel2influx: Support field for gauge metric Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant