docs: clarify metric aggregation temporality configuration for Microm… #15701
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eter Add documentation to clarify that metric aggregation temporality (DELTA vs CUMULATIVE) should be configured at the SDK/exporter level using the standard OpenTelemetry configuration property `otel.exporter.otlp.metrics.temporality.preference`, not at the Micrometer instrumentation level. This addresses confusion around how to configure temporality for metrics collected through the Micrometer bridge, explaining that: - Aggregation temporality is a data export concern, not a data collection concern - The Micrometer instrumentation creates metrics via the OpenTelemetry API - Temporality is determined by the configured metric exporter - SDK-level configuration affects all metrics consistently Fixes #issue-number
Author
|
Hey, In case there are issues regarding the problem , please do mention for my follow up. |
Member
|
hey @Arunodoy18 it's really great that you want to contribute to this project, but this is the 5th AI-generated PR you've opened, and so far none of the previous have been accepted or make a whole lot of sense. You might have a better chance of having a contribution accepted if you pick an issue that is well defined, or something that you understand. Also, I would suggest creating draft PRs until you have passing test suites. Hope this helps! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…eter
Add documentation to clarify that metric aggregation temporality (DELTA vs CUMULATIVE) should be configured at the SDK/exporter level using the standard OpenTelemetry configuration property
otel.exporter.otlp.metrics.temporality.preference, not at the Micrometer instrumentation level.This addresses confusion around how to configure temporality for metrics collected through the Micrometer bridge, explaining that:
Fixes #issue-number