Open for Voting

Calendar’s for maintenance windows, SLA’s, and production monitoring windows

Calendar’s for maintenance windows, SLA’s, and production monitoring windows

I know this has been beatup before but I am attempting to introduce this at the product core level to be available to all components

in order to increase product capacility, flexibility, and scalability.

Many shops these days varied production hours of operation, 24x7 schedules, maintenance windows and other recurring time periods where monitoring,  alerting, or the absence of applies.  The ability to define a schedule or calendar for various time periods is very helpful.  This calendar can then be applied to a monitor, an alert, a view, or even a report.  By doing so will reduce the number of alerts required to cover windows that vary over the period of a week.

In our environment, for example, we have a series of component monitors and alerts for two servers that monitor for existence of a process or service, MSMQ queue depth, log file update times, etc.  The challenge is that on Monday – Friday from 0200 – 0600 they are in a maintenance window so alerts should not happen.  To further compound this, the window changes on Saturday and again on Sunday to 0200 – 0700 and 0200 – 0800 respectively.  Now our alert count goes way up to compensate.  If the window changes due to business requirements we have to go in and touch a number of resources to adjust allowing for more opportunity to miss something.  To further exacerbate the situation, there are
other servers running related services also affected by this schedule.

So to have one schedule or calendar to define this window but able to be referenced by all of these aspects of the product makes it much easier to set up and maintain.  This results in fewer configuration points to have to touch when making updates therefore reducing chances for errors.  You can set up many different calendars for servers, interfaces, services, processes, monitors, alerts, etc.  This extends the capability of the product a great deal and makes it more scalable and flexible. 

This schedule also needs to be recurring in nature and as a core component available to all of the components of Solarwinds (NPM, SAM, WPM, Alerts, etc.)

Alert Central is not an option for us being it is a pre-rolled VM environment which goes against corporate policy by not being a company standard image.  Therefore it will never be installed here.

The functionality I speak of here is related to what I have seen in Telalert 6e and works very well.  In fact you can call from the command line the tool to see if a calendar is in effect to make use of it externally.