Centralized Alerting
ANOW! Observe sends structured alert payloads from Alertmanager to SolarWinds Incident Response. This helps consolidate alerts from various operational systems into a single platform for consistent incident management.
ANOW! Observe integrates with SolarWinds Incident Response (formerly Squadcast) to route operational alerts from Alertmanager to a designated alert source. This integration provides one-way delivery of actionable alerts, enabling teams to manage incidents effectively.
The integration routes operational alerts from Alertmanager, the Prometheus alerting component integrated in ANOW! Observe, to an alert source on a SolarWinds Incident Response service. This integration delivers notifications for workload automation incidents, such as job failures, SLA breaches, or anomalies, from ANOW! Automate or BMC Control-M. The alert source in SolarWinds Incident Response receives these events, which can then be used to create, update, or resolve incidents. The integration is one-way outbound; Alertmanager sends events to SolarWinds Incident Response, and no data is sent back to ANOW! Observe.
Alerts are triggered when Alertmanager routes a notification to a webhook receiver pointing at the alert source webhook URL. Alertmanager deduplicates, groups, and prioritizes alerts before sending them. The webhook receiver sends an HTTP POST with the standard Alertmanager JSON payload, including firing or resolved status, labels, annotations, timestamps, and the originating alert URL. The webhook URL, which acts as the only credential, should be treated as a secret and stored securely in the Alertmanager configuration. Communication uses TLS/HTTPS when configured accordingly.
This integration is for IT operations teams, platform engineers, and site reliability engineers in enterprises that use SolarWinds Incident Response as their primary incident management platform. It allows these teams to consolidate alerts from various operational systems within a single incident response workflow, streamlining their incident handling processes.
ANOW! Observe sends structured alert payloads from Alertmanager to SolarWinds Incident Response. This helps consolidate alerts from various operational systems into a single platform for consistent incident management.
Each alert payload includes mandatory fields like severity, summary, and description. This provides your incident response teams with the necessary context directly within SolarWinds Incident Response, supporting quicker understanding and routing of issues.
Notifications sent to SolarWinds Incident Response are part of the governed execution record on the ANOW! Observe side. Failed webhook deliveries are retried and logged, helping operators identify delivery issues.
The integration uses Alertmanager's generic webhook receiver, requiring only a webhook URL obtained from SolarWinds Incident Response. This simplifies setup, as no complex OAuth or bidirectional token exchange is required for this one-way data flow.
Use Cases
INCIDENT RESPONSE
Automatically route alerts for job failures and SLA breaches from workload automation into SolarWinds Incident Response.
IT OPERATIONS
Bring workload automation alerts into the platform where your other operational alerts are already handled.
DEVOPS
Send anomaly alerts from ANOW! Observe to SolarWinds Incident Response, where they can create new incidents.
COMPLIANCE
Failed webhook deliveries to SolarWinds Incident Response are retried and logged.
You need batch processing software that completes every job within the batch window across mainframe, SAP, and cloud. Yet one batch chain rarely stays on one system, and windows slip at the handoffs. When you need to migrate batch workloads, judge platforms by how far their dependencies reach and how vendors convert job definitions and calendars from your current scheduler. Here are the 7 platforms worth a shortlist.
Read article: 7 Best Batch Processing Software for Enterprise ApplicationsDo you have more questions?
The integration is configured in Alertmanager by adding a webhook receiver that points to the webhook URL generated for the alert source in SolarWinds Incident Response. This URL acts as the credential and should be securely stored in your Alertmanager configuration.
ANOW! Observe sends standard Alertmanager JSON payloads. These payloads contain the alert's firing or resolved status, labels (including mandatory severity), annotations (including mandatory summary and description), timestamps, and the originating alert URL.
No, the integration is one-way outbound. Alertmanager sends events to SolarWinds Incident Response, but the platform does not send data back to ANOW! Observe. Incident handling and response are managed by SolarWinds Incident Response.
Failed webhook deliveries are retried and logged, helping operators identify delivery issues. Notifications sent to SolarWinds Incident Response are part of the governed execution record on the ANOW! Observe side.
When an alert clears, Alertmanager sends a resolved notification, provided send_resolved is enabled in your Alertmanager configuration. SolarWinds Incident Response can use this notification to resolve the corresponding incident.
The ANOW! Observe integration with ServiceNow streamlines IT operations by automatically creating, updating, and resolving incidents and registering events. It ensures observability signals flow into ServiceNow with full workflow context, reducing manual intervention and accelerating incident resolution.
The Rootly integration routes operational alerts from Alertmanager, the Prometheus alerting component integrated in ANOW! Observe, to Rootly's Alertmanager alert source. This allows Rootly to create incidents and automate follow-up actions from ANOW! Observe notifications for workload automation events.
ANOW! Observe integrates with Parny, an on-call management and alerting service, to provide one-way delivery of actionable operational alerts. This enables enterprises to centralize workload automation incidents alongside other critical alerts in their primary on-call platform for efficient tracking and resolution.
ANOW! Observe integrates with ITOC360, an alerting and incident management platform, to route operational alerts one way into ITOC360. Alerts for job failures, SLA breaches or anomalies from ANOW! Automate or BMC Control-M arrive with a priority set from their severity label.
ANOW! Observe integrates with ilert to establish a one-way outbound connection, routing operational alerts to ilert. Workload automation incidents, such as job failures or SLA breaches, start ilert's on-call rotation and escalation policies.
The ANOW! Observe integration with HeyOnCall provides one-way outbound alert routing, delivering notifications for workload automation incidents directly to your on-call teams. Events such as job failures or SLA breaches reach whoever is currently on call.
Icinga is an open-source monitoring system for infrastructure and service health. ANOW! Observe can pass workload automation alerts to Icinga through a community-maintained webhook bridge.

Robusta is an open-source platform for Kubernetes monitoring and alert enrichment that runs inside the customer's own cluster. ANOW! Observe can forward alerts to a customer-operated Robusta instance through Alertmanager's webhook receiver.