Schedule Availability Monitoring

[Christopher_Chi]

How can I schedule availability monitoring?

[Anon]

If you need to monitor availability at a particular time or ignore avaiability during a maintenance window then you will need to do two things:

1. Create a Schedule in the SCHEDULE configuration
2. Attach the Schedule created in the Availability entity through the AVAILABILITY configuration


e.g.

I created a schedule called: IRSCHEDULE in the SCHEDULE Configuration and it will measure the availability weekly between Monday to Sunday from 8am to 9pm:

SCHEDULE ADDSCHED ( IRSCHEDULE, WEEKLY, MON-SUN, 08:00-21:00 )

Now in the Availability Configuration, I will attach this schedule to a particular Schedule called IRSCHEDULE:

APPLICATION SCHEDULE ("Windows", IRSCHEDULE)

I hope that helps.

[Anon]

Hi Chris,

Did this do the trick? Let me know.

Regards

Jitesh

[Kuanyu_C]

Can I tag along on this thread?

After we upgraded from 11.4 to 11.5, I have found that my Analyst no longer abide by the SCHEDULE.

This is what SCHEDULE looks like:
SUBSYS SCHEDULE
! Sample SCHEDULE configuration for use with Availability
! entities.
! WeekDaysBusinessHours Schedule
! ==============================
! This schedule is for entities that must be available
! during business hours on weekdays.
! Mondays to Fridays, 9:00am to 6:00pm
SCHEDULE ADDSCHED ( WeekDaysBusinessHours, WEEKLY, MON-FRI, 07:00-19:00 )
! Add in holidays for 2019 calendar year
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 01 JAN 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 21 JAN 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 18 FEB 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 27 MAY 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 04 JUL 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 02 SEP 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 14 OCT 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 11 NOV 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 28 NOV 2019, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 25 DEC 2019, 00:00-24:00 )
! Add in holidays for BB&T 2020 calendar year
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 01 JAN 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 20 JAN 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 17 FEB 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 25 MAY 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 04 JUL 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 07 SEP 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 12 OCT 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 11 NOV 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 26 NOV 2020, 00:00-24:00 )
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 25 DEC 2020, 00:00-24:00 )
! 24x7 Schedule
! =============
! This schedule is for entities that must be available
! all the time.
! Every day, midnight to midnight
SCHEDULE ADDSCHED ( 24x7, WEEKLY, MON-SUN, 00:00-24:00 )
! Sample weekly scheduled outage for, say, cold backups.
SCHEDULE EXCEPTION ( 24x7, WEEKLY, SUN, 00:00-03:00 )

 and this is the section in AVAILABILITY for Prognosis APPLICATION prior to 11.5.0 upgrade:

! Monitor "PROGNOSIS" as an application:
APPLICATION ADDTCPHOST ( "Prognosis", LOCAL_SERVER )
APPLICATION ADDEXE ( "Prognosis", IRNETRTR )
APPLICATION ADDSERVICE ( "Prognosis", "Prognosis" )
APPLICATION ADDPORT ( "Prognosis", 1960 )
APPLICATION ADDDISK ( "Prognosis", C: )

I have tried adding a new lne:

APPLICATION SCHEDULE ( "Prognosis", WeekDayBusinessHours )

but it does't seem to be doing the trick either.

[GeraldC1]

It looks like you have the right approach. It's just that it looks like you're just missing an 's' in your new line:
APPLICATION SCHEDULE ( "Prognosis", WeekDayBusinessHours )

Try this instead:

APPLICATION SCHEDULE ( "Prognosis", WeekDaysBusinessHours )

HTH

[Kuanyu_C]

Thank you for your response @GeraldC1 

I promise you, the typo is only in this post! In my environment it is matched up correctly between schedule declaration in AVAILABILITY and the addsched in the SCHEDULE module

Let me try to share again:
In AVAILABILITY
! Monitor "PROGNOSIS" as an application:
APPLICATION ADDTCPHOST ( "Prognosis", LOCAL_SERVER )
APPLICATION ADDEXE ( "Prognosis", IRNETRTR )
APPLICATION ADDSERVICE ( "Prognosis", "Prognosis" )
APPLICATION ADDPORT ( "Prognosis", 1960 )
APPLICATION ADDDISK ( "Prognosis", C: )
APPLICATION SCHEDULE ( "Prognosis", WeekDaysBusinessHours )

In SCHEDULE:

! Mondays to Fridays, 3:30am to 7:00pm
SCHEDULE ADDSCHED ( WeekDaysBusinessHours, WEEKLY, MON-FRI, 03:30-19:00 )

! Add in holidays for 2019 calendar year
SCHEDULE EXCEPTION ( WeekDaysBusinessHours, ONCE, 07 JUN 2019, 00:00-23:59 )

I added today's date to test the exception, but so far, I'm still getting Analyst alerts sending to my inbox.

I'll also add, not sure if this is relevant, but my Analyst rules are sending to DISPMAN profiles, rather than groups, so at this I am kind of suspecting tere is an underlying priority that allow DISPMAN Profiles overwriting SCHEDULE exceptions?

In ANALYST:

    string  _sprof01_g[30]      := "PF_MTS_Tech"     !WTOS and ADS-Wire

and in DISPMAN:

PROFILE ( PF_MTS_Tech, SUNDAY,,,,,,,,,,,,,,,,,,,,,,,, )
PROFILE ( PF_MTS_Tech, MONDAY,,,,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,,,,,,, )
PROFILE ( PF_MTS_Tech, TUESDAY,,,,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,,,,,,, )
PROFILE ( PF_MTS_Tech, WEDNESDAY,,,,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,,,,,,, )
PROFILE ( PF_MTS_Tech, THURSDAY,,,,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,,,,,,, )
PROFILE ( PF_MTS_Tech, FRIDAY,,,,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,MTS_Tech,,,,,,, )
PROFILE ( PF_MTS_Tech, SATURDAY,,,,,,,,,,,,,,,,,,,,,,,, )

[GeraldC1]

OK. Create a display of MpAvailability (AVMON) record, (start with all fields, and default where clause ALL ) to see what is happening inside the record and that ScheduleName (SCHDNAME) field contains the name of the schedule for the required entity row. See how the "ScheduledOutageInProgressflag" (SCHDOUT) field shows "Y" during the scheduled outage and otherwise "N".

Then add to the where clause in the threshold condition:

AND SCHDOUT="N"

That should stop alerts during the scheduled outage.

HTH