“I need to be notified if there’s a significant event ongoing with SignalFx.” This is what I tell my team. However, despite being the CTO of a monitoring company, creating the right set of alerts for me to stay informed of incidents in progress or potential issues was harder than it seemed at first glance. Why?
The pressure in the natural gas pipelines under three Massachusetts communities spiked to 12 times their normal level last week, just before the explosions and fires that destroyed dozens of homes and killed an 18-year-old man. Columbia Gas went under fire for their mismanagement of the incident. The NTSB says a Columbia Gas control room in Columbus, Ohio, registered pressures of 6 pounds per square inch last Thursday in pipelines that are intended to carry just 0.5 PSI.
Gift of Hope Organ & Tissue Donor Network is a non-profit organ procurement organization that coordinates organ and tissue donation and provides public education on donation in Illinois and northwest Indiana. As one of 58 OPOs that make up the nation’s donation system, Gift of Hope works with 180 hospitals and serves 12 million people in their donation service area.
In my previous post, I talked about the real costs of alert fatigue — the toll it can take on your engineers as well as your business — and some suggestions for rethinking alerting. In part 2 of this series, I’ll share some best practices for fine-tuning Sensu to help reduce alert fatigue.
Custom Metrics (JMX, Golang expvar, Prometheus, statsd or many other), APM and Opentracing are different approaches on how to instrument code in order to monitor health, performance and troubleshoot your application more easily.
Since you’re reading this blog, you’re likely aware of the most critical part of using Sentry: our client SDKs. We shared previously that we were updating Sentry’s SDKs, and now we’re on the verge of those updates becoming the default. This affects a few of our most popular platforms: Python and JavaScript, plus we also threw .NET and Rust into the mix for good measure.
When you’re building software, there’s so much to think about — from bugs to how fast your application loads. We’ve got something new to help your development team build better, faster experiences for your users, in less time. Today, we’re releasing Raygun Application Performance Monitoring (APM) for .NET, a new way to visualize and understand your application’s performance on the server-side.
A recent study from Mulesoft shows that 75% of enterprises have moved past the digital transformation planning stage to rolling up their sleeves and diving into implementation. Teams are updating their IT Operations Management (ITOM) strategies, moving more systems and services to the cloud, and automating tedious manual processes that have historically been the root cause of migraines for many people.
Achieving optimal performance can be challenging when you depend on separate platforms to monitor service health and to manage your logs. When data about your systems is spread across multiple platforms, investigating issues—and ultimately resolving them—takes longer and requires expertise with more tools. It takes more effort to identify real customer impact, as well as to verify that your responses to an incident are having the desired effect.
PM2 is a production-grade process manager that makes management of background process easy. In the Python world we could compare PM2 to Supervisord, but PM2 has some nifty features you might like. With PM2, rolling restarts, monitoring, checking logs and even deploying application has never been that simple. We really value CLI UX, so PM2 is really simple to use and master.
