Hi, For my use case, the usage of *honor_timestamps *parameter with false value is ok for my need. But, i search to know what the other impacts can be. Have you an idea?
Loïc Le mardi 20 juillet 2021 à 18:00:38 UTC+2, Loïc a écrit : > Hi, > > I have the following use case : > > - I use a cadvisor job that scraps the system metrics on the Kubernetes > nodes : > > *- job_name: node/cadvisor* > * honor_labels: true* > > * honor_timestamps: true* > * scrape_interval: 10s* > * scrape_timeout: 10s* > * metrics_path: /metrics/cadvisor* > * scheme: https* > * kubernetes_sd_configs:* > * - role: node* > * namespaces:* > * names:* > > * - <namespace>* > * bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token > <http://kubernetes.io/serviceaccount/token>* > * tls_config:* > * ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt > <http://kubernetes.io/serviceaccount/ca.crt>* > * insecure_skip_verify: true* > > - I use the *container_memory_working_set_bytes* metrics to retrieve the > RAM used by my containers. > - When i redeploy my pod, i have 2 sample by promql 'instant query" > (without the time parameter). Indeed, the sample related to the previous > pod/deployment is still returned during few minutes, > - If i set *honor_timestamps *to false instead true, i have only the last > sample active, it works. > > Could you more information on this parameter? > > Thanks > Loïc > > > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/51e26cc1-41d5-468f-ac78-f2d32f1905e9n%40googlegroups.com.
