-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[exporter] prometheusremotewrite appends _None to Datapoints with "Unit: None" #22828
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Is 'None' a valid unit according to the UCUM specification? I am not very knowledgeable about it, but have always seen If None is invalid, the problem is in the receiver instead of the exporter. |
@mx-psi - Those metrics I posted above are actually coming from the ecscontainermetrics receiver, not the dockerstats receiver. Either way, I don't think any exporter should be mutating metric names, regardless of the unit inference. Doing so brings about an aspect of chaos that brings into question the consistency/validity of the metrics, and especially impacts cross-version compatibility. |
Sorry, I posted the wrong link, I meant to link https://ucum.org, it should be fixed now :) In any case, I meant that whatever receiver is producing these is probably at fault.
As I understand it, this is something that should be done according to the opentelemetry specification:
If you think the spec should be changed or you want to understand why it works that way, I would suggest you open an issue over at https://github.com/open-telemetry/opentelemetry-specification; we won't change the behavior of the PRW exporter unless the specification itself changes. |
@mx-psi - Dang, so that's effectively going to break every single metric that has previously passed through the exporters. I think the PRW exporter should support this use case:
as a configuration value. What are your thoughts on that? That would adhere to PRW exporter to both parts of the specification. |
I don't have a strong opinion about this, I will defer to @Aneurysm9 and @rapphil |
I suppose I could use the |
Looks like this is the relevant discussion: #21743 |
Going to close this issue as this should ultimately be resolved by the decision made in the issue linked in the comment above ^ |
Component(s)
exporter/prometheusremotewrite
What happened?
Description
It seems that datapoints where the Unit has not been assigned (
Unit: None
) end up having_None
appended to the end of the metric name.Steps to Reproduce
_None
to the metrics.Expected Result
_None
not being appended to MetricsActual Result
_None
is being appended to MetricsCollector version
0.77.0
Environment information
Environment
Linux - Alpine
OpenTelemetry Collector configuration
Log output
The text was updated successfully, but these errors were encountered: