MACHINE_UNAVAILABLE ALARMS do not show up in WCC, Information: I141001 No matches for the search criteria were found

book

Article ID: 211046

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

WCC is not showing MACHINE_UNAVAILABLE alarms on the Dashboard below warning/error is seen:

Cause

MACHINE_UNAVAILABLE alarm is not tied to any jobs (job name is null). 

 

We need to ensure that appropriate Alert Policy definition and as-job permissions exist.    Let's say ACE is the Autosys Instance Name.  For the MACHINE_UNAVAILABLE alarm, WCC is checking for:   ACE.null    So, ACE.*   would be a better resource to check permissions against.

  

 

Environment

Release : 12

Component : WORKLOAD CONTROL CENTER

Resolution

On the Alert Policy in WCC,

1) Make sure  ALARM_TYPE = MACHINE_UNAVAILABLE   is one of the options that is selected.

2) Verify Active flag is checked ON, and one of the Servers in the Servers dropdown is selected ON.

3) WCC -> Configuration -> Monitoring preferences -> check whether Use AutoSys Workload Automation policies in EEM  is checked ON or not.   If it is checked ON, such Machine_Unavailable alarms base their permissions off of as-job  policy in EEM's WorkloadAutomationAE policy.  Ensure the user logged into WCC has appropriate as-job policy privilege,  

 

In this case, customer identified that the Autosys Instance Name.*  was missing on AE policy for prod.  Once appropriate resource, (PR1.*   in their case) was added to existing as job policy, that resolved the issue