Operations | Monitoring | ITSM | DevOps | Cloud

We added a series of improvements to our notifications settings, making it easier for you to control where your alerts are sent.

Even with a complete understanding of the benefits that come with running a hybrid environment, companies are still challenged with digital transformation best practices: what to move, when to move it, what’s being spent, how it’s performing, and what’s being overutilized and underutilized. This is why Amazon Web Services (AWS) is one of the most strategic partners in LogicMonitor’s ecosystem.

Nothing’s worse than getting a call from the users that the network is down. Too often, IT lacks the visibility they need to get before performance issues arise, meaning you’re in the dark until a user or customer calls to complain. Once an outage happens, the clock is ticking. And the more time you take to understand and resolve the issue, the more it costs you: in terms of customer dissatisfaction, and also staff time & lost productivity.

This article will cover the most common challenges you might find when trying to use Prometheus at scale. Prometheus is one of the foundations of the cloud-native environment. It has become the de-facto standard for visibility in Kubernetes environments, creating a new category called Prometheus monitoring. The Prometheus journey is usually tied to the Kubernetes journey and the different development stages, from proof of concept to production.

Docker is an essential bridge in modern DevOps. Despite Kubernetes overtaking Docker on orchestrating containers, the Docker container itself remains the standard and likely will for the foreseeable future. We developed the Docker Metrics collector to operate as its own container that will run Metricbeat using the modules you are running in real time. Now, in addition to the Docker module, we are now releasing an AWS module for operations in the cloud.

A few months ago, Honeycomb released our SLO — Service Level Objective — feature to the world. We’ve written before about how to use it and some of the use scenarios. Today, I’d like to say a little more about how the feature has evolved, and what we did in the process of creating it. (Some of these notes are based on my talk, “Pitfalls in Measuring SLOs;” you can find the slides to that talk here, or view the video on our Honeycomb Talks page).

Distributed tracing remains one of the most important features of any tracing system. Nearly a year ago, we announced Elastic APM distributed tracing, let’s take a look at how this useful feature works behind the scenes. Over the past few years, many applications have adopted microservice architecture. Each of the services in a microservice architecture can have their own instrumentation to provide observability into the service.

Being a UI developer, I’ve learned one thing: It doesn’t matter how carefully you write your code. Suppose you’ve double-checked that you defined and called all functions the right way or followed all the best practices. Even then you’ll see that a tiny variable can sneak behind and create an error. Now, suppose you find out that for some unknown reason a form validation or submit button isn’t working.

Coronavirus is changing everything. But amid all the talk of shut-downs, quarantine, and stock market crashes, another huge impact of the current crisis has been a little overlooked: it’s consequences for cybersecurity. With hundreds of thousands of employees now working from home – in the US, Europe, and all over the world – many companies have had to rapidly put in place systems for them to connect their home devices to corporate networks.