PagerDuty AIOps is the noise reduction, event correlation and event-driven automation add-on for the PagerDuty platform, built by PagerDuty, Inc., which applies machine learning to the alert stream before the incident reaches the on-call engineer. Licensed per accepted event, it bundles Global Alert Grouping, Auto-Pause Incident Notifications, Probable Origin, Global Event Orchestration and the Operations Console, and raises ingestion 120 to up to 10,000 events per minute per integration key.
PagerDuty AIOps is a noise reduction, event correlation and event-driven automation add-on for NOC, ITOps and SRE teams, built by PagerDuty, Inc., which applies machine learning models to the alert stream before the incident reaches the on-call engineer. It runs on the same event ingestion as PagerDuty Incident Management and is switched on service by service, through AIOps Service Configuration. It is SaaS, with no server to run and no model to train.
AIOps replaces Legacy Event Intelligence, unavailable to new customers since April 11, 2023, and swaps manual Rulesets for Event Orchestration. The problem it solves is the alert storm: one database failure that fires three hundred alerts across dozens of services and buries the on-call engineer in duplicate notifications. According to PagerDuty, early access customers saw an average 87% reduction in noise.
The product is organized into five feature sets: noise reduction, triage and root cause, event orchestration, operations console and increased ingestion.
The first benefit cuts notification volume without hiding incidents, because grouping happens at the alert level: alerts stay recorded and searchable in the Alerts Table, but produce one incident instead of three hundred. The second shortens triage, because Probable Origin and Recent Changes deliver the causal hypothesis alongside the page, instead of forcing the on-call engineer into the monitoring dashboard to find where it started.
The third removes manual work: Event Orchestration performs suppression, deduplication, enrichment and routing at ingestion, before any human is involved. The fourth protects peak operations, because the ingestion limit rises 120 to up to 10,000 events per minute per key on request.
PagerDuty AIOps is for teams whose event volume is high enough that noise is the main problem: centralized NOC, ITOps, platform engineering, SRE and SOC teams consolidating several monitoring tools into one queue. The buyer is usually the operations manager or the head of SRE; the person who feels the difference is the on-call engineer.
Three concrete scenarios: a NOC receiving events Zabbix, Nagios and Amazon CloudWatch that wants a single queue with Global Alert Grouping; an e-commerce operation whose peak produces bursts above 120 events per minute per key; a platform team that wants Dynamic Routing instead of maintaining a table of integration keys per service.
The first differentiator is requiring no implementation project: grouping models are switched on per service in the Noise Reduction screen and already run against the account's alert history, with no initial tuning and no knowledge base to build.
The second is cross-service reach — Global Alert Grouping and Global Event Orchestration act across the whole account, not inside a per-service silo. The third is correlation with code change: Recent Changes brings change events GitHub, GitLab and Jenkins onto the incident itself.
PagerDuty AIOps is an add-on: it requires a PagerDuty account on a Professional or Business Incident Management plan, or a Customer Service Operations plan. It is not sold standalone.
Being SaaS, access is through the web app on current stable versions of Google Chrome, Mozilla Firefox, Apple Safari, Microsoft Edge and Opera. Events arrive through the Events API v2, the PD-CEF format or an email integration, with a default limit of 120 events per minute per key. The account lives in a single service region, United States or European Union. Enabling or disabling AIOps per service requires a Manager, Admin, Global Admin or Account Owner base role.
PagerDuty AIOps is purchased by event volume tier: tiers up to Tier 5 appear on the Subscriptions screen and, above Tier 5, purchasing goes through the sales team. When the add-on is activated, every service and Event Orchestration has AIOps enabled by default.
The predecessor, Legacy Event Intelligence, was licensed per seat and remains available only to customers who already had it: it gets no new features and lacks Global Alert Grouping, Unified Alert Grouping, Global Event Orchestration, Dynamic Routing and the Operations Console. There is a 30-day trial; if it ends without a purchase, Noise Reduction, triage and dashboard settings are not preserved, while Advanced Event Orchestration rules are kept.
PagerDuty AIOps is licensed per accepted event, on a consumption model with volume tiers (draw-down). An accepted event is any valid event sent to and processed by PagerDuty; invalid events, events blocked by rate limits and events that returned an error response are not charged. The model is annual (subscription), with a multi-year option, and the add-on presumes a base Incident Management or Customer Service Operations plan.
There is no single list figure because the investment depends on sizing: annual accepted event volume, tier purchased, how many services have AIOps enabled, the base plan in use, and whether it is a new purchase or a renewal. Two rules change the math: events sent during a Maintenance Window do count, and only events directed to AIOps-enabled services draw down the tier. PagerDuty emails the Account Owner at 50%, 80%, 90%, 100% and 150% of the purchased volume. To buy PagerDuty AIOps in Brazil, OSB Software maps that scope with you, sends the commercial proposal, issues the Brazilian invoice and delivers the licenses — request a quote to get the exact figure for your scenario.
Can I buy PagerDuty AIOps without PagerDuty? No. AIOps is an add-on to an account on a Professional or Business Incident Management plan, or on a Customer Service Operations plan.
Does PagerDuty AIOps raise the events-per-minute limit? Yes. The default limit of 120 events per minute per integration key can be raised to 10,000 per key, on request to the account team or Support.
Can AIOps be enabled on only some services? Yes, through AIOps Service Configuration. A disabled service loses Alert Grouping, Auto-Pause, Probable Origin, Related Incidents, Past Incidents and Recent Changes, and reverts to the default ingestion limit.
Do Legacy Event Intelligence users have to migrate? Legacy Event Intelligence stays active for existing customers, but has received no new features since April 11, 2023; migration is handled by the sales team.
OSB Software is an official PagerDuty partner in Brazil and supplies 100% genuine PagerDuty AIOps licenses to companies, with Brazilian invoicing, local contracting in Portuguese and full legal compliance — the safe way to buy imported software under a Brazilian corporate entity, with no risk of irregular licensing.
When you buy PagerDuty AIOps OSB Software, you get:
If you are looking for where to buy PagerDuty AIOps in Brazil with legal certainty and properly licensed imported software, request a quote: OSB Software delivers reliable technology, qualified support and a simple, transparent purchase.
You don't know what software you need or you haven't found what you were looking for? We have a team ready to help you choose the right software for your company.