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

Setting TimeToBeReceived in the metrics configuration does not set the corresponding TimeToLive value #307

Merged
merged 1 commit into from
May 22, 2024

Conversation

mauroservienti
Copy link
Member

@mauroservienti mauroservienti commented May 22, 2024

The Metrics configuration, like all the other configuration options, exposes a way to set the metric message time to live.

Instead of using the canonical TimeToLive property, it's using TimeToBeReceived.

This PR fixes the bug by introducing a new TimeToLive property and obsoleting the wrong one.

Co-Authored-By: Brandon Ording <bording@gmail.com>
@danielmarbach danielmarbach merged commit 78a359e into release-2.0 May 22, 2024
3 checks passed
@danielmarbach danielmarbach deleted the backport-283-to-r2 branch May 22, 2024 12:45
@danielmarbach danielmarbach changed the title [Backport 283 to release-2.0] Metrics configuration wrongly exposes TimeToBeReceived instead of TimeToLive Metrics configuration wrongly exposes TimeToBeReceived instead of TimeToLive May 22, 2024
@mauroservienti mauroservienti changed the title Metrics configuration wrongly exposes TimeToBeReceived instead of TimeToLive Setting TimeToBeReceived in the metrics configuration does not set the corresponding TimeToLive value May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants