ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

DUAS: Alerts not applied to all launches

book

Article ID: 111863

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Alerting rules doesn't apply as expected for one / several launches, the Alert Icon is not displayed for the specific launch.
Command line give incoherent status for a given launch depending on the command used (uxlst fla or uxlst ctl) when compared with Univiewer Console - Job Runs.

Example:
An Alert Rule is defined to monitor Uproc launches that are in "Excessively Long Event Wait Status" based on an "Absolute Duration of two minutes"

A Uproc has a File Resource Condition that is never satisfied, so we would have the Alert Sent for all the launches, but in some cases it doesn't.
Sometimes the alert is sent and the script does the job that is to update the launch status changing it from "Event Wait" to "Time Overrun".
In that case, the command uxlst ctl shows that the status is "Time Overrun" but for the same launch, the uxlst fla show the status as "Event Wait"

Cause

In case of an important number of alerts to be launched, in a concurrent map access there is a problem and some alerts are not triggered

Environment

Dollar Universe 6 nodes using Alerting Rules

Resolution

Upgrade to Dollar Universe Application Server 6.9.41 or superior, available since October 2018.