-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[metricstarttimeprocessor] Add subtract_initial_point strategy #38379
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
Comments
Pinging code owners for processor/metricstarttime: @dashpole @ridwanmsharif. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label. |
This change implements the strategy defined in open-telemetry#38379.
This change addresses open-telemetry#38379.
This change addresses open-telemetry#38379.
This change addresses open-telemetry#38379.
This change addresses open-telemetry#38379.
This change addresses open-telemetry#38379.
This change addresses open-telemetry#38379.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This change addresses open-telemetry#38379.
…egy (#38594) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Addresses #38379. Some of this logic already existed in the [GCM exporter](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/main/exporter/collector/internal/normalization/standard_normalizer.go). For each resource, and for each timeseries - Skip if the point is not a cumulative sum, histogram, exp histogram, or summary. - Lookup the timeseries in the cache. If it is not present, drop this point from the batch, and store the timestamp and value (including bucket counts, etc) in the cache. - Subtract cumulative values (e.g. sum, bucket counts) of the cached timeseries from the current timeseries, and set the start timestamp to the cached point's timestamp. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #38379. <!--Describe what testing was performed and which tests were added.--> #### Testing Added unit and integration tests. <!--Describe the documentation added.--> #### Documentation Readme already covers this strategy <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Ridwan Sharif <[email protected]>
…egy (open-telemetry#38594) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Addresses open-telemetry#38379. Some of this logic already existed in the [GCM exporter](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/main/exporter/collector/internal/normalization/standard_normalizer.go). For each resource, and for each timeseries - Skip if the point is not a cumulative sum, histogram, exp histogram, or summary. - Lookup the timeseries in the cache. If it is not present, drop this point from the batch, and store the timestamp and value (including bucket counts, etc) in the cache. - Subtract cumulative values (e.g. sum, bucket counts) of the cached timeseries from the current timeseries, and set the start timestamp to the cached point's timestamp. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#38379. <!--Describe what testing was performed and which tests were added.--> #### Testing Added unit and integration tests. <!--Describe the documentation added.--> #### Documentation Readme already covers this strategy <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Ridwan Sharif <[email protected]>
…egy (open-telemetry#38594) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Addresses open-telemetry#38379. Some of this logic already existed in the [GCM exporter](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/main/exporter/collector/internal/normalization/standard_normalizer.go). For each resource, and for each timeseries - Skip if the point is not a cumulative sum, histogram, exp histogram, or summary. - Lookup the timeseries in the cache. If it is not present, drop this point from the batch, and store the timestamp and value (including bucket counts, etc) in the cache. - Subtract cumulative values (e.g. sum, bucket counts) of the cached timeseries from the current timeseries, and set the start timestamp to the cached point's timestamp. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#38379. <!--Describe what testing was performed and which tests were added.--> #### Testing Added unit and integration tests. <!--Describe the documentation added.--> #### Documentation Readme already covers this strategy <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Ridwan Sharif <[email protected]>
…egy (open-telemetry#38594) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Addresses open-telemetry#38379. Some of this logic already existed in the [GCM exporter](https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/main/exporter/collector/internal/normalization/standard_normalizer.go). For each resource, and for each timeseries - Skip if the point is not a cumulative sum, histogram, exp histogram, or summary. - Lookup the timeseries in the cache. If it is not present, drop this point from the batch, and store the timestamp and value (including bucket counts, etc) in the cache. - Subtract cumulative values (e.g. sum, bucket counts) of the cached timeseries from the current timeseries, and set the start timestamp to the cached point's timestamp. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#38379. <!--Describe what testing was performed and which tests were added.--> #### Testing Added unit and integration tests. <!--Describe the documentation added.--> #### Documentation Readme already covers this strategy <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Ridwan Sharif <[email protected]>
Component(s)
processor/metricstarttime
Is your feature request related to a problem? Please describe.
This is part of implementing the metricstarttime processor. This strategy is useful because is preserves semantics for cumulative metrics, meaning that the cumulative value between the start and end time is from observations that occured in that window.
Describe the solution you'd like
Describe alternatives you've considered
No response
Additional context
This is similar to what is done in the google exporters: https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/main/exporter/collector/internal/normalization/standard_normalizer.go
The text was updated successfully, but these errors were encountered: