The issue is due to the backup itself completing (or often even beginning) late so more than 24hrs passes. These backups run "late" by undetermined environmental factors in your systems. The alarm uses full day increments for comparison in determine late backups.
Example: Backup for a database starts at 10 PM, and runs until 12:30 AM, when it successfully completes. Using the default threshold for Warning(0.0-1.0 days), this would trigger a Warning severity level alarm.
The rule is functioning as designed.
WORKAROUND
Set the days since last backup to fire an alarm when the backup has not been run for two consecutive days.
Note: By default after adding a new database to an existing monitored instance, or creating a new agent will cause Foglight to fire a Warning alarm if it has not detected a recent backup. This is expected behaviour. Default collection for Backup data will run once per 24h or once per hour depending on the collection frequency and if the Foglight user is logged in(daytime) or logged out(overnight).
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center