feat(monitoring): parametrize data retention for plan-based config#61
Open
feat(monitoring): parametrize data retention for plan-based config#61
Conversation
Expose VM_RETENTION_PERIOD and QUERYID_RETENTION_HOURS through docker-compose so retention can be tuned per plan (Starter 7d, Scale 6mo). Defaults preserve previous hardcoded values. Helm chart already exposes both knobs via values.yaml.
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
2 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.
Expose VM_RETENTION_PERIOD and QUERYID_RETENTION_HOURS through
docker-compose so retention can be tuned per plan (Starter 7d,
Scale 6mo). Defaults preserve previous hardcoded values. Helm
chart already exposes both knobs via values.yaml.