-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
prometheusremotewrite exporter doesn't work well with groupbyattrs processor? #9981
Comments
@newly12 indeed this looks like a bug, but I am curious why do you need this processor in your pipeline? This does exactly opposite of what prometheus remote write protocol needs which is to "flatten" all the attributes as labels for each data point. |
This should be fixed by #9088 |
Thanks for the quick response. We are leveraging prometheus receiver to pull cadvisor metrics and also enrich the metrics given the |
For who may be interested, other issues with this approach #10021 #10023 |
Describe the bug
When
groupbyattrs
processor is enabled and useprometheusremotewrite
exporter in metrics pipeine, there will be failures/errors in prometheus translator at here probably because flags likepmetric.MetricAggregationTemporalityCumulative
are removed or ignored bygroupbyattrs
processor.Steps to reproduce
Please use the given config below to reproduce this error
Permanent error: invalid temporality and type combination
What did you expect to see?
things to work while having these 2 components in a metrics pipeline.
What did you see instead?
What version did you use?
Version: v0.50.0
What config did you use?
Config: (e.g. the yaml config file)
Environment
OS: MacOS 12.3.1
Compiler(if manually compiled): go 1.17.8
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: