UIM : RSP : Limitation of Windows Event Monitoring feature before and after probe restart

book

Article ID: 141644

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

This KB article explains an important limitation for rsp probe customers where Windows Event Monitoring profile is used.

When probe is restarted, in the entire probe level, Windows Event Monitoring feature is not working for some period of time.
As a result, alarm (related to Windows Event Monitoring) might not be generated even if event which meets watch criteria is happening before or after probe restart.
This behavior is limitation.

What period is affected by the limitation ?
It depends on how probe is restarted.

An example.
You have created Windows Event Profile monitoring that watches Job Failure event. The profile runs every 5 minutes polling interval.

(Senario #1)
Either of the following operations

a. Probe deactivate and activate.
b. Restart of rsp robot.
c. Probe restart via [Restart] menu, probe configuration change via Raw Configure.

  [16:02:00]  probe's polling
  [16:07:00]  probe's polling
  [16:12:00]  probe's polling
  [16:12:30]  Job 01 Failure event happened.
  [16:15:00]  probe deactivated and activated
  [16:15:00]  probe's polling
  [16:16:00]  Job 02 Failure event happened.
  [16:20:00]  probe's polling

In senario #1, Windows event that happened in between 16:12:00 and 16:15:00 are never checked.
As a result, rsp probe generates UIM alarm for Job 02 failure, but it does not generate UIM alarm for Job 01 failure.



(Senario #2)
[Apply] button submission over probe GUI to save any changes.
(*) It triggers probe restart internally.

  [16:02:00]  probe's polling
  [16:07:00]  probe's polling
  [16:12:00]  probe's polling
  [16:12:30]  Job 01 Failure event happened.
  [16:15:00]  [Apply] button submission over probe GUI
  [16:16:00]  Job 02 Failure event happened.
  [16:17:00]  probe's polling

In senario #2, Windows event that happened in between 16:12:00 and 16:17:00 are never checked.
Unlike senario #1, polling does not run until 16:17:00 after [Apply] button submission because internal timer for polling interval is not reset. 
As a result, rsp probe does not generate UIM alarm for both events.


Environment

RSP probe (All Version)

Resolution

Please use ntevl probe.
There is no such limitation in ntevl probe.

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/ntevl-nt-event-log-monitoring/ntevl-nt-event-log-monitoring-release-notes.html

Additional Information

There are some improvement in RSP 5.35 HF1.
See 5.35 HF1 Readme for details.

https://techdocs.broadcom.com/us/product-content/recommended-reading/technical-document-index/ca-unified-infrastructure-management-hotfix-index.html

Attachments