Everybody's "best" time is likely to be different depending on their needs, tolerances, reaction time, email infrastructure, network capacity, etc., etc. The more frequently you check, the more load you put on your system which will impact other services and users. You probably should discuss with your stakeholders what would be the maximum time between an event happening and someone being notified about it. Then you have to factor in, how long does it take to get the event into Splunk, how long does it take to get the email out, how long does it take for someone to notice that an email has arrived, how long does it take for them to get into Splunk or reporting system to see the event, etc. Once you have some of these answers, pick a schedule that comes close without overloading your systems and try it out, and be prepared to tweak it. To be honest, it will probably never be right for everyone, but you will probably have to make some compromises.
... View more