We’re excited to announce that one of the most popular feature requests is finally here: BugSplat now supports Dark Mode! Whether you’re burning the midnight oil or just prefer a more eye-friendly interface, Dark Mode is here to make those late-night debugging sessions a bit more comfortable.

At BugSplat, we always advocate for teams to introduce crash reporting and establish a bug-tracking/bug-fixing workflow early in their development process. So you can imagine my excitement when I found myself at Denver Startup Week chatting with the founder of a startup that has several projects in flight. He mentioned they’d just kicked off development of a new application, and things were moving quickly.

Solving system failures and performance issues can be like solving a tough puzzle for engineers. But trace data can make it simpler. It helps engineers see how systems behave, find problems, and understand what's causing them. So let’s chat about why trace data is important, how it's used for finding the root cause of issues, and how it can help engineers troubleshoot more effectively.

In this article, you will learn effective ways on how to manage IT costs. Recently, IT departments face increasing pressure to reduce costs while maintaining high-quality services. A McKinsey and University of Oxford study found that large IT projects, on average, run 45% over budget and 7% over time while delivering 56% less value than predicted. This alarming trend emphasizes the need for effective IT cost management strategies.

Effective incident alerting is crucial for businesses to maintain smooth operations and customer satisfaction. Incidents often generate multiple alerts, each requiring timely and transparent handling to ensure a swift resolution. Ensuring transparency throughout the incident alert process can be challenging. This is where SIGNL4 steps in, offering a comprehensive solution that enhances transparency at every step of incident alert handling.

A quieter month this time around: you can now customize your status pages, there are additional overall statuses for status pages, and I fixed a few bugs.

In the observability space, ease-of-use has always been a key differentiator for Grafana. As much as we want to offer a powerful observability platform to our users, we also want to ensure they can get up and running as quickly as possible. Still, for those of you sitting down to build your first dashboard, we totally understand that a little guidance can go a long way.

Are incident reviews about learning or tracking actions? This question has sparked recent debate in incident management circles, including in my recent panel at SEV0 and in Lorin Hochstein’s post. Should the goal of an incident review be learning, or should it focus on tracking actionable improvements? When is the right time to discuss actions, and are they picked up just to make us feel better? From my experience, learning from incidents and identifying actions are inseparable.