Incident Management

Rootly

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.

Rootly

About the Integration

The Rootly integration connects ANOW! Observe with Rootly, an incident management platform. This one-way outbound integration sends operational alerts from ANOW! Observe to Rootly, where they can trigger incident workflows and automated follow-up actions. It specifically delivers notifications for workload automation incidents such as job failures, SLA breaches, and anomalies.

Technically, the integration uses Alertmanager's generic webhook receiver. Alertmanager sends an HTTP POST with the standard JSON payload to Rootly's incoming webhook URL. This payload contains alert status (firing or resolved), labels, annotations, timestamps, and the originating alert URL. Authentication uses a bearer token issued by Rootly, set in the receiver's http_config.

This integration is for platform and operations teams who use Rootly as their incident management platform of record and rely on ANOW! Observe for comprehensive workload automation monitoring. It helps bridge the gap between operational event detection and structured incident response.

Integration Benefits

Centralized Incident Creation

ANOW! Observe sends structured alert payloads from Alertmanager to Rootly. Rootly-side workflows use these notifications to create or update incidents, consolidating operational event response within your chosen incident management platform.

Automated Follow-Up Actions

Alerts from ANOW! Observe, detailing job failures or SLA breaches, can trigger Rootly's automation capabilities. This allows for automated follow-up actions, reducing manual steps in your incident response processes.

Rich Alert Context

The integration delivers detailed Alertmanager JSON payloads, including labels like alertname, instance, dc, job, status, and version. This provides Rootly with extensive context for each alert, aiding in accurate incident classification and routing.

Reliable Alert Delivery

Notifications sent to Rootly are part of the governed execution record on the ANOW! Observe side. Failed webhook deliveries are retried and logged, helping operators identify delivery issues.

Use Cases

Workflows Supported by This Integration

INCIDENT RESPONSE

Trigger Incidents from Workload Failures

Automatically create Rootly incidents when ANOW! Automate jobs fail, using Alertmanager notifications.

OPERATIONS

Page On-Call Teams for SLA Breaches

Route SLA breach notifications from ANOW! Observe to Rootly for on-call paging.

MONITORING

Auto-Resolve Incidents on Condition Clearance

Automatically mark Rootly alerts as resolved when the underlying operational condition clears in ANOW! Observe.

AUTOMATION

Customize Paging Targets per Alert Rule

Define specific Rootly users, groups, or services to page directly from Alertmanager alert rules.

Get more insights

Blog Article

7 Best Batch Processing Software for Enterprise Applications

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 Applications

FAQs

Do you have more questions?

Explore similar integrations

Ready to start your journey?