In Sybase ETL 4.9, you can set alerts at the occurrence of runtime events such as, project or job start, complete, or error. You can configure ETL to send E-mail alerts when any of these events occur:
You can specify multiple email addresses to subscribe
to an ETL event notification.
Jobs – notifies when a job starts, finishes successfully, or finishes abruptly with errors.
Job Start – occurs when a job is started, and contains the job name, the grid engine on which it is running, and the time it started.
Job Finish – occurs when a job is finished normally, and contains the job name, the grid engine on which it was running, the start and end time of the job, and the list of all the projects.
Job Error – occurs when a job finishes with errors and contains details like job name, grid engine name, time start, time failed, and the error message.
Projects – occurs when a project starts, finishes successfully, or ends abruptly with errors.
Project Start – occurs when a project starts and contains details like project name, grid engine on which it started, and the time it started.
Project Finish – occurs when a project ends successfully and contains information such as project name, the grid engine name on which it was running, project start and end time, and the number of rows successfully loaded.
Project Error – occurs when a project ends abruptly with errors. The mail has details like project name, the grid engine name on which it was running, project start and failed time, number of rows successfully loaded, and the error messages.
Multiple grid node processes running on the same grid
engine share the same alert service configuration file and alert
history log file.
Use the Alert Manager from the ETL Development GUI to create, edit, and delete alert definitions. You can create multiple alerts for any event type for project simulation and job and project execution. However, the alert name must be unique.
You can view event alert history in the File Log Inspector as well as on the ETL Web interface. You can also set filter conditions while mapping an alert. For example, you can define a filter to check for only a specific project name to trigger an alert.
Sybase ETL 4.9 also supports storing all the alert history in a separate log file for help during troubleshooting.
Sybase recommends you to set up email alert notifications on one machine. You can then manually copy alert configuration file across different grid engines running on the network.
See Chapter 4, “Advanced Concepts and Tools” in the Sybase ETL 4.9 Users Guide.
