Monitoring and Alerting

Owned by Former user (Deleted)
Dec 03, 2019

Overview

The Monitoring and Alerting feature of Universal Agent provides for the monitoring the status and activity of all Universal Automation Center Agents in an enterprise and the posting of alerts regarding the statuses.

Monitoring is provided through continuous Monitoring of All Agents or by Querying for Job Status and Activity of a specific Agent.

Monitoring of All Agents

Universal Agent provides for the continuous monitoring of all Agents in an enterprise through its Universal Enterprise Controller component.

Monitored Information

Universal Agent monitors for three types of information:

  1. Alerts for all Agents and SAP systems being monitored
  2. Jobs (active, completed, and failed) for all Agents being monitored
  3. Systems (Agents and SAP systems) being monitored

This information can be viewed via the I-Activity Monitor UEC client application.

Polling

Universal Agent periodically polls each Agent and SAP system in an enterprise in order to retrieve its status information.

It determines whether or not a change in status of the Agent or SAP system has occurred since the last poll. If the status has changed, it sends this information to the I-Activity Monitor.

Alerts

Universal Agent sends out alerts to any connected Agent-monitoring applications whenever:

  • Agent is unreachable.
  • Agent is not responding.
  • Agent component enters an orphaned or disconnected state.

These alerts are posted to the:

  • Event Log (when running under Windows)
  • Console (when running under z/OS)

Automation tools can be used in conjunction with these messages to perform operations based on agent failures.

Querying for Job Status and Activity

Universal Agent has the ability to query any specific Universal Broker in an enterprise for Broker-related, and active component-related, activity via the Universal Query utility.

Universal Query returns information for a Universal Broker that is installed on the host, as specified by configuration options on the command line or in a configuration file. Information regarding the components managed by a particular Universal Broker also can be requested.

Universal Query registers with a locally running Universal Broker. Consequentially, a Universal Broker must be running in order for a Universal Query to execute.

Additional Information

The following pages provide additional detailed information for Monitoring and Alerting: