Operations | Monitoring | ITSM | DevOps | Cloud

Today, IT operations teams have to process large volumes of events or alarms in near real-time in order to protect service levels, stay competitive, and deliver a great experience to customers. If it takes too long for teams to spot and repair issues, an organization runs the risk of significant business service downtime, SLA penalties, and brand reputation damages. As IT landscapes continue to grow in scale and complexity, guarding against these risks becomes increasingly difficult.

Today, I’m excited to announce that Gerald Combs, the original creator and lead maintainer of Wireshark, has joined Sysdig. In addition, Sysdig is becoming the primary sponsor of Wireshark.

It was a Wednesday in November, and we had just wrapped Grafana Labs' third virtual Grafana Cloud offsite of 2021. Outside my window, it was a dark and cold (8 degrees Celsius) night in Cologne (Köln), Germany. In Austin, Texas, it was early afternoon and headed for 80 degrees Fahrenheit. In Cape Town, South Africa, it was a windy and cool spring evening. And in Melbourne, Australia, our final speaker — who was up very early at 5 a.m. — was heading into a cool spring day.

If you have set up your own monitoring services with Amazon CloudWatch, Azure Monitor or another internal tool, we suggest you consider looking beyond the horizon. These services often provide internal web monitoring only. Perhaps they validate HTTP availability from locations outside their networks, but HTTP checks won’t give you a 360º view into the state of your services.

The world revolves around DevOps tools. DevOps engineers go insane when they have too many tools. The first statement is correct. Also, the second one. Tooling that helps in the automation of software development and infrastructure provisioning workflows and pipelines is critical for both the engineers who create the automations and the developers who use the automated workflows on a daily basis.

With dozens of microservices running on multiple production regions, getting to a point where any error log can be immediately identified and resolved feels like a distant dream. As an observability company, we at Coralogix are pedantic when it comes to any issue in one of our environments. That’s why we are using an internal Coralogix account to monitor our development and production environments.