Operations | Monitoring | ITSM | DevOps | Cloud

OpenNMS alarms now reach ilert through a dedicated plugin that runs inside OpenNMS. Network and infrastructure teams get a direct path from an alarm on a device, interface, or service to the phone of the engineer on call. The ilert alert then follows the alarm: accepted when it is acknowledged, resolved when it clears.

The AlertOps Experience Update is rolling out to every AlertOps customer. It reorganizes the web app around the way an incident runs, starting with a left-side menu that keeps every part of AlertOps one click from any screen. This post walks through what you will see when you log in, where everything lives now, and a few things worth trying first. Your data, schedules, escalation policies and integrations carry over exactly as they are, so there is nothing to migrate or reconfigure.

The PagerDuty Microsoft Teams integration gets incident notifications into Teams channels and lets responders acknowledge and resolve from there. It does not turn Teams into your on-call tool. It will not answer "who is on call for payments?" from a channel, it cannot post into private or shared channels, and it needs three different admins to set up. If your company runs on Teams, you should know exactly where that line falls before you design your incident process around it.

Picture the bridge call at 2 am. A Sev1 has taken down a critical service, and the paging storm has pulled forty people out of bed, even though only six of them will ever touch the fix. The first hour disappears into roll call and trying to figure out which changes shipped last night, which alerts are related, and who actually owns the failing service.

When a critical incident occurs, reaching the right person quickly can make all the difference. Whether it’s a hospital contacting an on-call physician or an IT team responding to a server outage, reliable paging software helps ensure urgent messages reach the people responsible for taking action. Traditional pagers have long been used in hospitals, emergency services, and other mission-critical environments.

Being responsible for the reliability of services people count on every day isn’t easy. Customers expect everything to work, all the time, and when it doesn’t, someone has to answer for it. Whether you need to get yourself out of bed at 3 a.m. or step away from a family dinner, your job is to quickly diagnose the problem and fix it to ensure your operations get back up and running quickly before customers notice. But it doesn’t always go like that.

Today, we’re introducing Paige, PagerDuty’s SRE Agent. Built on over 16 years of operational data, Paige works as a member of operations, engineering, and DevOps teams, coordinating signal intelligence, incident management, and automation. Paige learns from every incident, so every incident improves the next response. Each resolution is written back into shared memory, making every response sharper than the last.

Incidents are inevitable. Spending three meetings arguing over whether your incident management process is actually improving is slightly more avoidable. Either way, avoiding adverse conditions begins with one element: consistent measurement. For most teams, a handful of incident management KPIs provide a reliable picture of performance from the moment something goes wrong through to final resolution.

Configuration Management Databases (CMDBs) have long played an important role in IT Service Management, providing a structured record of technology assets, their configurations and relationships. For enterprises managing complex IT environments, they remain a valuable foundation for understanding infrastructure and supporting operational processes.

For a small practice, choosing an electronic health record system affects nearly every part of the working day: documenting visits, prescribing medications, reviewing results, scheduling appointments, and submitting claims. The right choice should fit your clinical specialty and the way your team operates.