Automate testing of agents communication and recieved email notifications when there is a problem
search cancel

Automate testing of agents communication and recieved email notifications when there is a problem

book

Article ID: 253653

calendar_today

Updated On:

Products

Autosys Workload Automation CA Workload Automation AE - Scheduler (AutoSys)

Issue/Introduction

In an environment with 1200+ agents, there is a need to implement an automated communictions testing of the agent's process and notify of exceptions.

Understanding that the autoping command can achieve this, it doesn't make sense to create 1200+ jobs to accomplish this task.

What other options are available?

Environment

AutoSys: All versions

Resolution

There are several methods to achieve this requirement. Depending on the client's need one option might be better than another.

  • Option 1:
    Set up a job to run the following command
    autoping -m  ALL  -A

    This will perform a ping test at the application level of all agents defined in the Autosys Database.

  • Option 2:
    If you want to see an email with a list of missing/offline machines:
    Have a CMD job run autorep -M ALL every minute, and grep any Missing/Offline rows output to std_out.
    If > 0 rows FA the job and have set send_notification and email_template(STDOUT) accordingly.

    NOTE: A flaky network or high-load agents could result in a lot of noise so maybe increase to a 5-minute or higher run interval

  • Option 3:
    If they want to see it in WCC:
    WCC Alerts can be configured to watch for MACHINE_UNAVAILABLE alarms and display them on their GUI widget.

  • Option 4:
    Have a custom script monitor ujo_machine.mach_status via direct SQL through SQL job type, send an email periodically with any M/O machines.

    NOTE: This is a pretty good option because it doesn't involve expensive autoping/autorep -M ALL calls for 1200 agents.

Additional Information