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.

Sign up for GitHub

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

Add metrics retention documentation #353

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Add metrics retention documentation #353

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions documentation/monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,3 +157,12 @@ If connections start failing because of port exhaustion we alert on this as an e
Unfortunately we can't alert which kubernetes service is using aa high number of ports so this is a troublshooting exercise following:

[Troubleshoot SNAT port exhaustion on Azure Kubernetes Service nodes](https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/connectivity/snat-port-exhaustion?tabs=for-a-linux-pod)

## Metrics Retention

Metrics retention is based on sampling
- Raw data(actual data captured) is retained for 30 days.
- 5m down samples are retained for 60days
- 1hr down samples are retained for 90 days.

More information on down sampling is available on this [link](https://thanos.io/v0.8/components/compact/#downsampling-resolution-and-retention)
Loading