Skip to content
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

Update cassandra counters to be non-monotonic where appropriate #113

Merged
merged 2 commits into from
Oct 15, 2021

Conversation

dehaansa
Copy link
Contributor

Description: Two cassandra counters are non-monotonic, and should be treated as such.

Decrement example for load.count: source
Decrement example for total_hints.in_progress.count: source

@dehaansa dehaansa changed the title Update cassandra counters to be non-monotonic where appopriate Update cassandra counters to be non-monotonic where appropriate Oct 14, 2021
@dehaansa
Copy link
Contributor Author

Integration test appears to have failed for kafka metrics validation, so could that get re-run by whoever comes through to review?

@rmfitzpatrick
Copy link
Contributor

@dehaansa would you mind rebasing to include the fix for this issue? 323f91e

Copy link
Contributor

@rmfitzpatrick rmfitzpatrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@rmfitzpatrick rmfitzpatrick merged commit 3627c83 into open-telemetry:main Oct 15, 2021
@dehaansa dehaansa deleted the cassandra-non-monotonic branch October 15, 2021 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants