We’re running PMM Server v3.1.0 deployed in Kubernetes using the official Helm chart. As part of our configuration, we’ve explicitly set the following in our Helm values to retain metrics for 90 days
pmmEnv:
DATA_RETENTION: "2160h" # 90 days
Despite this setting, we’re seeing that metrics are only being retained for 30 days, the default retention period. This same configuration works as expected on PMM Server 2.x, where metrics are correctly retained for the full 90-day duration.
It seems that in PMM 3.x, this configuration might not be fully applied via Helm alone. The documentation suggests that retention settings may also need to be configured from the UI, which wasn’t required in the 2.x series.
We would appreciate clarity on this behavior. Specifically:
- Does PMM 3.x require the
DATA_RETENTIONsetting to be applied through the UI even if it’s already provided via Helm? - If so, is there a recommended way to configure retention in a fully automated and declarative manner for Kubernetes deployments?
Environment Details:
- PMM Server version: 3.1.0
- Deployment: Kubernetes using official Helm chart
We’d appreciate your guidance to ensure this is correctly configured in PMM 3.x.
