Follow-up objective: Specific process completes in error on a specific server
The IBM® Sterling Control Center Monitor administrator for the CD1 server group, needs to know when a specific process (DailyGrind) on a specific server (hawaiiCD) completes in error.
The CD1 administrator wants to generate a high-severity alert and be notified by email when an error occurs. To accomplish this objective, the administrator created the following building blocks:
Daily Grind Error action
When the Daily Grind process encounters an error on the hawaiiCD server, the administrator for the CD1 server group wants IBM Sterling Control Center Monitor to generate an alert and send an email. To accomplish this objective, the administrator created the following action. (This action was later selected when the “Daily Grind” rule was defined.)
| Field | Value |
|---|---|
| Name | Daily Grind Error |
| Description | Action taken when the DailyGrind process completes in error on hawaiiCD server. |
| To | Ops1@bank.com |
| From | SCCAdmin@bank.com |
| Subject | &processName; error |
| Message | &processName; completed in error on &nodeName; |
| Alert Severity | 1 - High |
| Permissions (Roles that can edit this action) | Operations Admin CD1 |
Daily Grind Error rule
Mike defined the following information for the rule and then placed the Daily Grind Error rule higher in the priority sequence than the Process error rule:
| Field | Value |
|---|---|
| Name | Daily Grind Error |
| Description | This rule is triggered when the DailyGrind process completes in error on any monitored server |
| Parameters | |
| Key | Event Type |
| Operator | Matches |
| Value | Process Ended |
| Key | Process Name |
| Operator | Matches |
| Value | DailyGrind |
| Key | Servers and Server Groups |
| Operator | Matches |
| Value | hawaiiCD |
| Key | Return Code |
| Operator | Not Equal To |
| Value | 0 |
| Action | Daily Grind Error |
