Graphite won't graph more than 2 days of data

[log1c]

Hm, I have the exact same config in the storage schemas, but have only the following inside the storage aggregation config:

[default]
pattern = .*
xFilesFactor = 0
aggregationMethod = average

Quoting from

@blakehartshorn

xFilesFactor describes what to do with null values. This is a floating point number from 0 to 1. The default is 0.5, so if one time period has less than 50% of the time points defined, that becomes null as it moves backward. This often isn’t ideal. In my case, I have a lot of 1m intervals set for checks that only run every 5 minutes. I like this because when it starts doing the retries in soft state, I get a more detailed view of what’s going wrong. If I used 0.8, my graph would just disappear the second it aggregates. By setting it to 0, I’m saying that I don’t care how few of the time points are used, if there are any, do something with it. 0.1 is another good option.

If I understand your config correctly you would aggregate all [dot]min & [dot]max files with the 0.1, the [dot]count file with the 0 setting and all other files with the 0.5 setting.
As my folders typically hold

• crit.wsp
• min.wsp
• value.wsp
• warn.wsp

I could suspect that those would all be aggerated with the [default] part from the config and maybe that’s why the values disappear after two days.

But tbh this is some wild guessing from my side and I am happy my graphite setups currently work

Only thing I can tell you for certain:

@emboehm

/var/spool/icinga2/perfdata.
Could this be the problem?

Those files are not needed for graphite, as graphite receives the perfdata directly from the core via a TCP connection configured in config for the graphite feature.
You can safely disable the perfdata feature if you don’t use it for anything else (it is deprecated anyway).