--late-campaign-starting-warning MINUTES
Number of minutes a campaign has to start its sending process for WARNING, when the queue is not full (Default 3)
Current: 3; Recommend: No change
--late-campaign-starting-critical MINUTES
Number of minutes a campaign has to start its sending process for CRITICAL, when the queue is not full (Default 5)
This is the one that tripped today. It cleared 10 minutes and 30 seconds after the initial failure was detected.
Current: 5; Recommend: 15
--late-campaign-starting-warning-queuefull MINUTES
Number of minutes a campaign has to start its sending process for WARNING, when the queue is full (Default 45)
Current: 45; Recommend: No change
--late-campaign-starting-critical-queuefull MINUTES
Number of minutes a campaign has to start its sending process for CRITICAL, when the queue is full (Default 45)
Current: 45; Recommend: No change
--late-campaign-sending-warning MINUTES
Number of minutes a campaign has to start sending once its sending process has begun for WARNING (Default 10)
Current: 10; Recommend: No change
--late-campaign-sending-critical MINUTES
Number of minutes a campaign has to start sending once its sending process has begun for CRITICAL (Default 15)
This tripped last week when a campaign took just over 20 minutes to start sending. This one is heavily affected by the increased size of the suppression database.
Current: 15; Recommend: 30