Issue with changing alarm severity for RSP probe

Document ID : KB000102314
Last Modified Date : 20/06/2018
Show Technical Document Details
Introduction:
Multiple monitoring profiles configured in the rsp probe using the default alarm severity for the service state metric for multiple services configured in all profiles.  Need a way to change the alarm severity for the service state for all monitored services for all configured profiles without going in and making the change to each individual service checkpoint in each profile.
Question:
How do you change the alarm severity for all configured inst_default service state monitors defined in every configured monitoring profile in the rsp probe?
Environment:
UIM 8.51
rsp - any version through 5.30
Answer:
All service->state monitors for each profile was created as a Profile override (static monitor). That means that any changes make to the service->state template are not automatically picked up any of the static monitors. This is by design - a static profile is designed to override the template. When creating service monitors from the Admin Console, they are all static monitors by default. When creating service monitors from Infrastructure Manager, you are given the option to create a static (Profile override) or a Template monitor.  Template monitors use the alarm level from the service->state setting in the probe's template section.  Static (profile override) monitors are always assigned an alarm level of major for service monitors.

There is no designed means of automatically changing the alarm level of the service->state alarm from the rsp probe Configure GUI for static service monitors. That would be considered an enhancement request.

In the meantime, there are at least 3 ways that can be used to change the current alarm level of the state alarm for all static servcie monitors. Unfortunately, all methods require touching all currently configured profiles.

Here are the 3 methods listed from the easiest/fastest to the hardest/longest.

In all 3 cases, it is highly advise that you save a backup copy of the current rsp.cfg file before making any changes so that you can get back to a known monitoring state should you make a mistake or set up undesirable monitoring with the changes you make. You can quickly get back to a known state by replacing the current rsp.cfg file with the backup copy then restart the rsp probe:

Method 1:
Using a text editor like notepad++, locate and change the following key value pairs found in the <profiles> section if the rsp.cfg file:

level = 4

to the new value (for example, to set a warning alarm level):

level = 2

Save the changes then restart the rsp probe.

Method 2:
From the rsp probe's Configure GUI opened from Infrastructure Manager, go to each profile in the left-hand pane, then right-click each of the windows services monitors in the right-hand pane and select the "Clear override" option. Once this has been completed for all profiles, Apply the changes and restart the probe. This will force the profiles to use the template monitors which should use the alarm level you have configured for the template->services->state alarm.

Method 3:
Again, from the rsp probe's Configure GUI opened from Infrastructure Manager, select the Advanced Configuration Mode button from the top.
Expand the Profile Templates node
Expand the Windows node
For each profile listed under the Windows node, do the following:
- Expand the profile node
- Expand the services node
- For each service
- Exapnd the service name node
- Select the State node
- In the right-hand pane, right-click the Aalrm level key, and select the Edit alarm condition... option
- In the Alarm Condition properties pop-up window, change the level from the current level (major) to the desired level (warning)
- Select OK

After completing the alarm level change for all currently defined static service monitors in all configured profiles, apply the change then restart the rsp probe.