Today I am excited to announce we have officially shipped PagerTree 4.0! Here are the highlights: This effort has been a year and half in development and I sincerely want to thank each and every one of our customers for the constructive feedback, ideas, and countless hours on Zoom calls. Without you this journey wouldn’t be possible. We are excited to get this major release shipped, just in time for the holidays. You can check out the full details of the upgrade below.

Welcome to the companion post to So You Received an Alert. Now What? Last time, we broke down the process between receiving the Uptime.com check alert and figuring out what broke. Today, we’re going to show you how to communicate your efforts so that everyone – your end users, coworkers, and bosses – know what’s going on. Your first step is to update your Status Page, your central hub for incident management and communication.

Forethought is a leading AI company providing customer service solutions that transform the customer experience. As a high-growth startup with a fast-expanding engineering org., teams had to deal with compounding complexity, leading to challenges measuring the impact and health of their services. Forethought’s core engineering team maintains common services between other internal teams, infrastructure, data, and tools and, as they added more engineers, the original team split into five.

Of growing concern to both patients and the professionals who facilitate their care is the growing trend of healthcare organizations being preyed upon by cybercriminals. In the United States, recent political dialogue has brought special attention to patients’ privacy rights under HIPAA and the ongoing security of their records.

Alert noise, as well as false positives or too few alerts, undermine the effectiveness of any monitoring solution. Inaccurate alerts condition users to draw poor conclusions. Too many alerts contribute to serious alerts going undetected. Too many false positive or non-actionable alerts cause the significance of all alerts to diminish over time. And too few alerts can lead to misreading system performance and missing critical problems.

When building alerts, engineers aim to create accurate, timely, and actionable alerts. In pursuit of this goal, many engineers will leverage PromQL throughout their careers. PromQL is the query language used by Prometheus and Alert Manager to query metrics and define alerting rules. While PromQL works very well for simple use cases, as infrastructure scales, architectural patterns grow more complex, engineering practices accelerate, and alerting use cases become more multivariate.