Recommendations for monitoring AutoSys as it relates to Postgres

Products

• Autosys Workload Automation

Issue/Introduction

Guidelines for proactively monitoring AutoSys logs when the system is configured with a PostgreSQL database.

Resolution

To maintain system health and stability, you should monitor the AutoSys Application Server (as_server) and Event Server (event_demon) logs for specific error patterns related to database connectivity and operations.

Standard Error Formats to Monitor

• CAUAJM_E_18200: This is a general error indicating an interface failure with PostgreSQL. It is the functional equivalent of the CAUAJM_E_18400 error used in Oracle environments.

• CAUAJM_E_18201: This indicates a specific function failure (e.g., Function <executeQuery> invoked from <execute> failed at <nnn>). The values within the brackets will change depending on the specific database operation that failed.

• CAUAJM_E_18202: This identifies a failure to load PostgreSQL client libraries. A common example is: libssl.so.3: cannot open shared object file: No such file or directory.

Monitoring Best Practices

1. General Monitoring: Set up automated scans of both as_server and event_demon logs specifically looking for any string starting with CAUAJM_E.

2. Case-Insensitive String Search: Configure your monitoring tools to alert on the string "postgresql" regardless of case.

3. Alert Configuration: Use these message formats to trigger alerts in your enterprise monitoring console, following the same logic used for Oracle-based AutoSys implementations.