Operations | Monitoring | ITSM | DevOps | Cloud

When you put Auvik on a network for the first time, the software automatically starts monitoring that network for more than 40 potential issues. When Auvik finds an issue, it triggers an alert. Network alerts range in severity from emergency at the top all the way down to informational. As you work with Auvik, you may see a lot of alerts coming your way. It’s obvious you need to deal with the emergency and critical network alerts. But what about the simple warnings and informational alerts?

It’s the middle of the workday and suddenly your IT team starts receiving calls: systems are slow, applications are unresponsive, and productivity grinds to a halt. Before you know it, you’re scrambling to pinpoint the issue and juggling complaints, all while the clock is ticking and downtime costs are piling up. The problem?

In the latest release of Turbo360, significant improvements have been made to the Business Activity Monitoring (BAM) module. This module is designed to shift support “left,” meaning it empowers support operators to identify and address issues earlier in the process by providing them with a business-friendly view of the underlying complex infrastructure.

A 502 Bad Gateway error implies that the server (Nginx) can’t properly communicate with the upstream web application server. A sign of more severe problems, such as server overload, improper configuration, or network failure, a 502 Bad Gateway error can cause service interruption, which can translate to revenue loss. Fortunately, you can easily resolve the error in Nginx once you identify the causes.

Apache Kafka’s thing is real-time data streaming. But keeping it running at full throttle? That takes more than just spinning up a cluster and hoping for the best. As your environment grows, you’ll need to do some tweaking to make sure Kafka keeps up with the pace. The good news? You don’t need to be a Kafka wizard to make a real difference. Even some basic tuning can have a big impact on performance.

At Honeycomb, we know how important it is for organizations to have a unified observability platform. This is why we’re launching Honeycomb Telemetry Pipeline and Honeycomb for Log Analytics: to enable engineering teams to send and analyze data—including logs—into a single, unified platform. For too long, teams have had to wrangle large volumes of logs, their context scattered across multiple teams and tools, leading to knowledge silos.

In a previous article, Julian provided a comprehensive overview of the characteristics and functionality of Incidents in Icinga Notifications. In today’s blog, I will explain the concept of Incident muting and its underlying mechanisms.