Netdata metrics retention


Is it possible to retain metrics data when metrics retention have not been set yet? The previous retention config have been set to default. Now, we cannot view our past data(from last week). Is there any way to view the data for the past week/month? Thank you.

Hi, for configuration of data retention. Do we still follow this config? Do we need separate update iteration config for tier 0 and tier 1? I want to have a view of 1 month’s worth of metric monitoring. Need advise on this. Thanks.

Hello @jerometeano, I would love some more context.

  1. What’s your Netdata deployment (netdata -W buildinfo)?
  2. Is a Netdata deployment via Docker?
  3. Did you recently updated and you can’t see the metrics you are looking for or it happened spontaneously?
  4. For the node in question, what’s the workload ( I mean what’s the metrics collected on avg) In the screenshot below you can find this info for your case):

In a nutshell, you allocate space for Netdata to use and it depends on your system workload how it translates to retention in days.

Relative topics to visit:

  1. Database engine | Learn Netdata explore the tiering mechanism
  2. Change how long Netdata stores metrics | Learn Netdata

Hi Tasos,

I think Im getting the idea of it. But to answer your questions, here are the details youre asking.

  1. Build info
    Version: netdata v1.36.1
    Configure options: ‘–build=x86_64-redhat-linux-gnu’ ‘–host=x86_64-redhat-linu x-gnu’ ‘–program-prefix=’ ‘–exec-prefix=/usr’ ‘–bindir=/usr/bin’ ‘–sbindir=/ usr/sbin’ ‘–datadir=/usr/share’ ‘–includedir=/usr/include’ ‘–sharedstatedir=/ var/lib’ ‘–mandir=/usr/share/man’ ‘–infodir=/usr/share/info’ ‘–prefix=/usr’ ’ --sysconfdir=/etc’ ‘–localstatedir=/var’ ‘–libexecdir=/usr/libexec’ ‘–libdir= /usr/lib’ ‘–with-zlib’ ‘–with-math’ ‘–with-user=netdata’ ‘–disable-dependenc y-tracking’ ‘build_alias=x86_64-redhat-linux-gnu’ ‘host_alias=x86_64-redhat-linu x-gnu’ ‘CFLAGS=-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE= 2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-s witches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redha t/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-cl ash-protection -fcf-protection’ ‘LDFLAGS=-Wl,-z,relro -Wl,-z,now -specs=/usr/li b/rpm/redhat/redhat-hardened-ld’ ‘CXXFLAGS=-O2 -g -pipe -Wall -Werror=format-sec urity -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-pro tector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-c c1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchron ous-unwind-tables -fstack-clash-protection -fcf-protection’ ‘PKG_CONFIG_PATH=:/u sr/lib/pkgconfig:/usr/share/pkgconfig’
    Install type: binpkg-rpm
    Binary architecture: x86_64
    Packaging distro:
    dbengine: YES
    Native HTTPS: YES
    Netdata Cloud: YES
    ACLK Next Generation: YES
    ACLK-NG New Cloud Protocol: YES
    ACLK Legacy: NO
    TLS Host Verification: YES
    Machine Learning: YES
    Stream Compression: NO
    protobuf: YES (system)
    jemalloc: NO
    libcap: NO
    libcrypto: YES
    libm: YES
    tcalloc: NO
    zlib: YES
    apps: YES
    cgroup Network Tracking: YES
    perf: YES
    slabinfo: YES
    Xen: NO
    Xen VBD Error Tracking: NO
    AWS Kinesis: NO
    GCP PubSub: NO
    MongoDB: NO
    Prometheus Remote Write: YES
  2. Deployment is in Linux machines.
  3. I have updated the config this week after losing the datas from last week. I hope to retain the data for this month starting from Monday,(05/09/2022) or since I have configured the DB engine.
  4. I cannot see the metrics summary since I am using Netdata cloud.