Is your feature request related to a problem? Please describe.
When an RRA is created, the heartbeat is normally defined as twice that of the data source profile (from what I've seen). However, if you switch profiles and miss recreating or migrating any of the RRA's, this can lead to gaps in the graph:
Turns out it was the minimal_heartbeat setting in the rrd that was the problem.
I've been dealing with odd issues here and there since upgrading from 0.8.8 to 1.2.2. One of them seems to be that my 5 minute polling data profile has a heartbeat setting of 2 minutes (120 seconds) after the upgrade.
Describe the solution you'd like
There should be a check and warning when the heartbeat is below the minimum cycle of a profile.
Additional context
I'm not sure whether this already appears on the Troubleshooting -> Data Sources section.
Is your feature request related to a problem? Please describe.
When an RRA is created, the heartbeat is normally defined as twice that of the data source profile (from what I've seen). However, if you switch profiles and miss recreating or migrating any of the RRA's, this can lead to gaps in the graph:
Describe the solution you'd like
There should be a check and warning when the heartbeat is below the minimum cycle of a profile.
Additional context
I'm not sure whether this already appears on the Troubleshooting -> Data Sources section.