The ANOW! Observe PagerDuty integration connects through its built-in Alertmanager component, forwarding alerts and incident events to PagerDuty. This integration sends structured incident events containing vital information such as severity, a summary of the issue, the affected job or workflow, runtime context, and a deep link back to ANOW! Observe. This robust connection ensures critical workload automation incidents, like job failures or SLA breaches from ANOW! Automate or BMC Control-M, trigger immediate, disciplined responses.
This integration connects using the standard Alertmanager PagerDuty receiver, which utilizes the PagerDuty Events API and a service-specific integration key. This approach aligns seamlessly with your existing PagerDuty service models, ensuring configuration consistency. ANOW! Observe deduplicates, groups, and prioritizes alerts before they reach PagerDuty, preventing alert fatigue and ensuring on-call rotations are paged only for genuine incidents. It supports routing notifications to different PagerDuty services or escalation policies based on criteria like team, severity, or business service.
This integration is designed for enterprise IT operations teams, SREs, and platform engineers managing complex hybrid IT landscapes. It is particularly valuable for organizations that rely on PagerDuty for their incident response and on-call management, needing to extend this discipline to their critical workload automation and mainframe operations.