… or am I overly ambitious?
Im planning to aggregate the data series of some checks regarding it’s intervall in several different ways to ensure best Graphite-Graphs in icingaweb2.
So here’s what my mind came up with:
I’ll define those services with names that contain information about the planned intervall, for example “HTTP5min” or “VPNTunnel1hour” or “NumberOfUsers90sec” or “Updates1day”.
Then I’ll define my retentions in the storage-schemas configuration as follows:
[carbon] pattern = ^carbon\. retentions = 60:90d [icinga_internals] pattern = ^icinga2\..*\.(max_check_attempts|reachable|current_attempt|execution_time|latency|s tate|state_type) retentions = 5m:7d [icinga_90sec] pattern = ^icinga2.*90sec.* retentions = 90s:2d,6m:10d,30m:90d,360m:4y [icinga_120sec] pattern = ^icinga2.*120sec.* retentions = 120s:2d,10m:10d,60m:90d,360m:4y [icinga_5min] pattern = ^icinga2.*5min.* retentions = 5m:2d,30m:90d,360m:4y [icinga_10min] pattern = ^icinga2.*10min.* retentions = 10m:2d,60m:90d,360m:4y [icinga_15min] pattern = ^icinga2.*15min.* retentions = 15m:90d,360m:4y [icinga_30min] pattern = ^icinga2.*30min.* retentions = 30m:90d,360m:4y [icinga_1hour] pattern = ^icinga2.*1hour.* retentions = 60m:90d,360m:4y [icinga_6hours] pattern = ^icinga2.*6hours.* retentions = 360m:4y [icinga_12hours] pattern = ^icinga2.*12hours.* retentions = 720m:4y [icinga_1day] pattern = ^icinga2.*1day.* retentions = 1440m:4y [icinga_default] pattern = ^icinga2\. retentions = 1m:2d,5m:10d,30m:90d,360m:4y [default_1min_for_1day] pattern = .* retentions = 60s:1d
For each intervall a seperate section with the matching pattern and retention.
Does this make any sense at all, or would you say “Hey geek what the heck are you doing there?”
Wide open for enlightment,