Skip to content
Support Portal
  • There are no suggestions because the search field is empty.

Introduction to AlertOps

Purpose

Understand what AlertOps does, how it routes alerts to the right person, and where it fits in your incident-response stack. Read this first if you are evaluating AlertOps or onboarding a new team onto it.

Audience

Relevant for all users

This article is written for anyone new to AlertOps — prospective customers doing an evaluation, new users going through onboarding, and experienced users who want a refresher on how the pieces fit together.

Typical readers include:

  • IT Operations and NOC teams.
  • DevOps engineers and Site Reliability Engineers (SREs).
  • Operational Technology (OT) and Data Center teams.
  • Incident responders and on-call engineers.

What You Will Learn

  • The core capabilities of AlertOps: alert routing, on-call scheduling, escalations, and integrations.
  • How an alert flows through the platform from the moment it is detected to the moment it is resolved.
  • Where to go next once you want to start configuring the platform for your team.

Prerequisites

None. This article is an overview — no account or configuration is required to read it. If you want to follow along in the product, you can start a free trial at alertops.com.

How AlertOps Works

AlertOps is an incident alerting and notification platform. Its job is to make sure the right person is notified, at the right time, when something goes wrong. An alert moves through six stages:

  1. Event ingestion. A monitoring, ticketing, or custom tool fires an event at AlertOps.
  2. Smart routing. The event is evaluated against routing rules to decide severity, recipients, and notification methods.
  3. On-call scheduling. The alert is mapped to whoever is on-call, based on shifts, rotations, and overrides.
  4. Escalation policies. If the first responder does not acknowledge in time, AlertOps escalates through a configured chain.
  5. Notification delivery. Notifications go out via SMS, voice call, mobile push, or email.
  6. 200+ pre-built integrations, plus any custom tool that can send a webhook, email, or REST API call.

Example — One alert, end-to-end

1. At 02:14, Datadog detects that an API's p95 latency has crossed the alerting threshold and fires a webhook at AlertOps.

2. AlertOps creates an alert tagged "API — Tier 1" and evaluates routing rules to match it to the API Reliability escalation policy.

3. The policy looks up the API Reliability on-call schedule and finds Priya as primary.

4. Priya is paged via SMS and mobile push at 02:14:03. She does not acknowledge within 5 minutes.

5. At 02:19, AlertOps escalates to the secondary on-call. He acknowledges from the mobile app at 02:19:41.

6. AlertOps stops escalating and records the full timeline on the alert for a post-incident review.

 

Key Capabilities

  • Smart alert routing based on severity, service, or source.
  • Custom on-call schedules with rotations, overrides, and out-of-office coverage.
  • Multi-level escalations so no incident falls through the cracks.
  • 200+ pre-built integrations plus generic webhook, email, and REST API support for anything custom.
  • Alert noise reduction through precise routing, filtering, and de-duplication.
  • Mobile apps and live-call routing for responders who are away from a desk.

Next Steps

Once you have the big picture, the next moves depend on where you are in your journey:

  • Evaluating AlertOps: start a free trial or email sales@alertops.com for a guided walkthrough.
  • Onboarding a new team: jump to the Quick Start Guide for a hands-on setup.
  • Existing customer with a support question: email support@alertops.com or call +1 (844) 292-8255.