-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Prometheus Receiver translates metrics to OTLP metrics with non-cumulative temporality #1541
Comments
I replaced Prometheus receiver with a OTLP receiver; the metrics remained cumulative and was exported successfully. |
I have the same issue but I am using prometheus receiver with file exporter, I only see gauge metrics. My metrics are exposed in prometheus format, so I am left with the choice of using prometheus receiver. |
An update on this issue. This is the log I am getting from the Prometheus remote write exporter:
This shows the OC to OT translation is setting the temporality to INVALID_TEMPORALITY(not setting it at all perhaps?); this makes the metrics not pass the check of the Prometheus remote write exporter. |
With OTLP v0.5 temporality translation is added. The Prometheus receiver works with the remote write exporter |
* Rename otel/label -> otel/attr Leave the imported name alone, to avoid a large diff and conflicts * Better import comment * Update CHANGELOG.md Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com> * otel/attr -> otel/attribute * Missed the changelog entry * Get rid of import renaming * Merge remaining conflicts Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com> Co-authored-by: Anthony Mirabella <a9@aneurysm9.com>
* initial version of the pulsar exporter (metrics). Tests yet to be added. (open-telemetry#1541) authored-by: Shiva Param <sparam@paypal.com> authored-by: Narasimha Rao <narasirao@paypal.com> authored-by: narasimharaojm <madhunarasimharao@gmail.com> * pulsarexporter: fix lint, remove failing tests (open-telemetry#1682) This is an experimental component added by PayPal. Unit tests to be added later.
I am doing an end-to-end test for the Prometheus remote write exporter in PR #1525, and I am using the Prometheus receiver to get input metrics.
In the process, I discovered counter, histogram, and summary Prometheus metric scraped by the Prometheus receiver are not exportable by the remote write exporter, but gauge metrics are exported. This is because the remote write exporter drops non-cumulative monotonic int64, monotonic double, histogram, and summary, but doesn’t check the temporality on int64/double OTLP metrics.
The Prometheus receiver seems to translate counter, histogram, and summary metrics into OTLP metrics with non-cumulative temporality. Is this the expected behavior or should the Prometheus receiver/translation gets modified?
If this is the expected behavior, what’s an alternate receiver to use to ensure cumulative metrics of different types will not be dropped by the exporter?
cc @huyan0 @alolita @jmacd @bogdandrutu
The text was updated successfully, but these errors were encountered: