Notifications Section Overview
Theme: Overview | Who is it for? Administrators and automation engineers who configure OpCon notification delivery
What Is It?
OpCon notifications fire when jobs or schedules reach specific status conditions. Notification triggers define the condition (job failed, schedule completed, etc.) and the delivery action (email, text message, SNMP trap, Windows Event Log, etc.). Groups and categories organize triggers; escalation rules ensure critical alerts are not missed.
When Would You Use It?
- Use this feature when jobs or schedules reach specific status conditions
Why Would You Use It?
- Operational value: Ensure critical alerts are not missed
When would you use this section?
- Setting up email or text alerts for failed jobs
- Configuring SNMP traps or Windows Event Log entries for system monitoring
- Defining escalation rules so alerts are re-sent if not acknowledged
- Troubleshooting a notification that is not being sent
What is in this section?
| Topic | Description |
|---|---|
| Notification Triggers | Concepts and configuration for job and schedule notification triggers |
| Notification Configuration | Server-level notification settings (SMTP, SMS gateway, etc.) |
| Notification Components | Components involved in notification delivery |
| Escalation | Escalation rules and groups for unacknowledged notifications |
| Manage Notification Triggers (SM) | Solution Manager interface for notification trigger management |
| Notification Categories | Organizing triggers into named categories |
| Notification Groups | Defining recipient groups for notification delivery |
| Notification Types | Delivery channel configuration — email, text, events, SNMP, and more |
| Escalation Manager | Solution Manager interface for escalation rule and group management |
Glossary
| Term | Definition |
|---|---|
| Escalation | A notification mechanism that repeats or elevates an alert if it is not acknowledged within a defined time period. |
| Event (OpCon Event) | A command string that OpCon runs when a defined condition is met, such as a job finishing, a threshold being updated, or a schedule completing. |
| Job | A task or activity defined in OpCon, such as running a program on a remote machine, transferring files, or running a sub-schedule. |
| Notification | An alert generated by the SMA Notify Handler when a machine, schedule, or job reaches a defined status. Notifications can be sent as email, text, SNMP, or Windows Event Log entries. |
| Role | A named collection of privileges that can be assigned to one or more user accounts. Users in a role inherit all of that role's privileges. |
| Schedule | A named group of jobs in OpCon that represents a business process. Schedules are built each day based on their defined frequencies and calendars. |
| SMTP (Simple Mail Transfer Protocol) | The protocol used to send email notifications from OpCon when jobs, schedules, or machines trigger notification events. |
| Solution Manager (SM) | The browser-based web interface for OpCon. Provides access to operations, self-service, vision dashboards, and configuration. |
FAQs
Q: Who manages Notifications in OpCon?
Administrators, automation engineers, and operations staff configure Notifications, manage user access, and monitor related processes.
Q: Where should I start in the Notifications section?
Begin with the overview pages in the sidebar. If you are new to this area, review access and role requirements with your OpCon system administrator before making configuration changes.