SQL Server Error Count Rule takes an hour to fire an alarm (4308356)

It takes 45 minutes and sometimes up to an hour to generate an alarm when the Error Count rule detects an error in the SQL Server log (e.g. Error: 17806, Severity:20, State:2). Why?

With the collection set to run in the offline mode at 3600 seconds, that would result Foglight checking the error log every hour when no one is in Foglight. When someone is in Foglight (online) it would check every 15 minutes, and if someone is in the Error Log area (realtime) the cycle would be five minutes.

You could lower these values. In addition, the offline timing cannot be less than the online or realtime times.

Please refer to KB 177914 for details on changing a database agent collection frequency.

The default collection times for the SQL Server cartridge

Collection Name: (offline sec, online sec, real-time sec, query timeout sec)
Error_Log_Check 3600, 900, 300, 60
Error_Log_List 3600, 900, 300, 60
DBSS_SQL_Agent_Error_Log 900, 300, 300, 300
DBSS_SQL_Server_Error_Log 900, 300, 300, 300