Graphite Data Archive


Hello together,

I am using Icinga 2 + Graphite with some hosts and services. Every 30sec there is a file created with all the values that were monitored. This takes a lot of storage.

I want to comprimize the data that is older than one year and archive it. How do you guys handle this problem?


(Michael Friedrich) #2

Please show the output of

icinga2 --version

icinga2 feature list

and how you’ve configured the Graphite feature.


Application information:
Installation root: /usr
Sysconf directory: /etc
Run directory: /run
Local state directory: /var
Package data directory: /usr/share/icinga2
State path: /var/lib/icinga2/icinga2.state
Modified attributes path: /var/lib/icinga2/modified-attributes.conf
Objects path: /var/cache/icinga2/icinga2.debug
Vars path: /var/cache/icinga2/icinga2.vars
PID path: /run/icinga2/

System information:
Platform: CentOS Linux
Platform version: 7 (Core)
Kernel: Linux
Kernel version: 3.10.0-693.2.2.el7.x86_64
Architecture: x86_64

Build information:
Compiler: GNU 4.8.5
Build host: unknown

Disabled features: api compatlog debuglog gelf influxdb livestatus opentsdb statusdata syslog
Enabled features: checker command graphite ido-mysql mainlog notification perfdata

What do mean with how i configured the graphite feature?

My storage-schemas.conf looks like this:
pattern = ^carbon.
retentions = 60:90d

pattern = ^icinga2.
retentions = 1m:90d,5m:10d,30m:90d,360m:4y

pattern = .*
retentions = 60s:90d

(Michael Friedrich) #4

Why is that feature enabled, if you’re using graphite already? You don’t need those spool files on disk from the perfdata feature.