Here's an example of an email that contains the bug.
In this example, the script has been configured to email a summary at 20:00 every day. An error had occurred (at 20/10/2012 03:18:05) in the previous interval so it should not appear in this email which covers the period (20/10/2012 20:00:01 to 21/10/2012 20:00:00).
Or, if it does appear, it should be clear that it does not fall within the period.
Message sent at 21/10/2012 20:00:00 from ServiceMon (v188.8.131.52), running on [REDACTED]
Script Module Live - Marketing Site has been running since 19/10/2012 15:37:34
Module 'Live - Marketing Site':
6 operations performed in Round-Robin order, with 1000 ms between each invocation
The maximum age of any error is 100 days.
When the monitor colour changes, emails will be sent to: [REDACTED]
At 20:00 every day, a summary email will be sent to: [REDACTED]
Colour thresholds: Not monitoring: Gray, 0 to 0.9 success-rate: Red, 0.9 to 0.99 success-rate: Pink, 0.99 to 0.999 success-rate: Orange, 0.999 to 0.9999 success-rate: LightGreen, 0.9999 or more success-rate: Green, otherwise White
The state is currently Green
• Error details: Sent at 20/10/2012 03:17:39: (Fetch content from 'http://[REDACTED]/'
using HTTP GET and expect the response to contain '[REDACTED]') Error occured at 20/10/2012 03:18:05: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host
Summary (since last report)
(20/10/2012 20:00:01 to 21/10/2012 20:00:00)
85486 Requests have been sent and received.
• 85486 were successful
• 0 failed
The current success rate is 100.000%