From fcc71df43aa2d4e54ceaff6fe74902b520283576 Mon Sep 17 00:00:00 2001 From: vipin-dfe Date: Thu, 16 Jan 2025 10:12:11 +0000 Subject: [PATCH] Add metrics retention documentation --- documentation/monitoring.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/documentation/monitoring.md b/documentation/monitoring.md index af3d9043..8c69f5b8 100644 --- a/documentation/monitoring.md +++ b/documentation/monitoring.md @@ -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)