[receiver/postgresql] Fix for inflated metric values in query metrics collection#43072
Merged
Merged
Conversation
Contributor
Author
|
@antonblock could you review this quick PR please? Thanks |
antonblock
approved these changes
Oct 1, 2025
VihasMakwana
approved these changes
Oct 1, 2025
Contributor
|
This is already approved by a codeowner. We can merge this if we can get an approval from @open-telemetry/collector-contrib-approvers . |
braydonk
approved these changes
Oct 1, 2025
Contributor
|
Thank you for your contribution @sv-splunk! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey. |
6 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
Description
Fix for inflated metric values in query metrics collection (postgresql). In each metric collection the delta of metric values are added into the cache instead of adding just the latest counter value. Which results in an inflated metric value on each following collection.
Link to tracking issue
Fixes #43071
Testing
Unit tests updated
Documentation