Introduce log retention gauge #3326
Merged
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
heavycrystal
reviewed
Aug 8, 2025
heavycrystal
approved these changes
Aug 8, 2025
Amogh-Bharadwaj
force-pushed
the
log-retention-gauge
branch
from
c3cfdd1 to
ef3c5b8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a float64 gauge for collecting log retention hours in MySQL and Mongo. It does this in the recordSlotSize workflow.
Introduces a new activity to call in that workflow called
emitLogRetentionHours.Utility functions in retention.go and mongo.go
Functionally tested locally with prometheus and grafana: