Home  Administration > Application Administration > Service Level Management Administration > Downtime Events > Event Examples



Event Examples

This section provides examples of events for all scheduling periods, and contains the following topics:

Once

Every morning the VP of eBusiness looks through the previous day's SLAs Summary reports. One morning, she realizes that due to maintenance in the Springfield office, the Web applications server had been down for three hours and all Business Process Monitor CIs from that location have failed. She needs to define a retroactive downtime event and adjust the reports to reflect the downtime.

Daily

The operations support engineer is told that a server's graphics card is being upgraded for a new map application. A slowdown of the server may be expected for three days beginning today, while the R&D team tests the new application. To minimize problems, the team will be running tests for one hour each day. All SLAs that monitor this server will be affected, and he should define an event to appear in reports to explain the slowdown.

Weekly

Example 1: You define an event to occur once every two weeks (2) with a start date of Tuesday, 7 Jun 05. For calculation purposes, the first week runs from Monday, 6 Jun 05 till Monday, 13 Jun 05.

Calendar

Example 2: You define a recurring event that occurs every second week on a Friday and a Sunday, to begin on a Saturday. In the first week, the event will run only on Sunday. In the second week, the event does not run. In the third week, the event runs on Friday and on Sunday, and so forth.

Calendar with recurring event

Monthly

Every other month, on the forth Sunday, the Web server for the Finance department in the Unionville office is scheduled for maintenance at 1:00 AM for two hours. Therefore, the IT Ops director must define a recurring event and exclude all CIs from reports during this period.

Yearly

The VP of eBusiness likes to be prepared. Each July 5th, her boss sends her an e-mail requesting network statistics for the previous day to compare to their targets. This year, on July 3rd, she prepares an SLA to measure network performance and creates an event that will run throughout the next 24 hours.

In the Scheduling section, she chooses the Yearly option. In the Frequency section, she selects Every, July, and 4. She enters the start date and time of July 4th at 12:00 AM and sets an event duration of 23 hours and 59 minutes. She leaves No end date selected.

On July 5th she is able to reply immediately to her boss's e-mail with the network performance results compared to the target objectives.




Copyright 2006 Mercury Interactive Corporation