Operations | Monitoring | ITSM | DevOps | Cloud

On Monday, October 20th, a significant portion of the digital services we use every day became inaccessible. For hours, banking, communication, and entertainment applications were unavailable. The root cause was later identified as a major outage within Amazon Web Services (AWS), the infrastructure that powers a vast number of online services. The initial response for any business affected by such an event is a frantic effort to diagnose the problem. Is it our application? Is our network down?

Since VMware joined Broadcom, there’s been some speculation in the industry about the future of Voyence, VMware's trusted network configuration management (NCM) solution. We want to address that speculation directly and share some exciting news.

Over the last few months IncidentHub has added several new features to make it easier to fine tune your alerts. IncidentHub now also integrates with Microsoft Teams and supports custom domains for your public status pages. Let's take a comprehensive look at what's new.

This post kicks off a new series written by the Graylog Development Team. In these updates, we’ll highlight the features and fixes that make daily work in Graylog smoother. We want to show the work we care so much about and present the challenges we faced and overcame. Today, we’re starting with one of those minor but functional enhancements: Graylog time-range stepping.

In part one of this series, we set up basic performance monitoring for our Fastify application using AppSignal and explored key performance indicators. Now that we have our monitoring foundation in place, it's time to leverage these insights to actively improve application performance. You'll learn how to detect performance regressions, find optimization opportunities, and implement custom instrumentation with OpenTelemetry.

Every hour developers spend troubleshooting is an hour they’re not building features, innovating, or delivering value to customers. Yet in most organizations, issue management and debugging remains one of the biggest drains on productivity and release velocity. That frustration is exactly what led our founders, themselves developers, to create Lightrun.