In part one, we introduced the duality of observability, controllability. As a reminder, observability is the ability to infer the internal state of a "machine” from externally exposed signals. Controllability is the ability to control input to direct the internal state to the desired outcome. So observability is a loop problem. And we need to stop treating it as the end state of our challenge in delivering performant, quality experiences to our users and customers.

The waves of change are certainly upon us and businesses are being forced to adapt at a record pace. Current world events have caused a jarring shift in all aspects of our lives, accelerating major changes in how we live and work. An unprecedented number of people are now working from home. Those of us working in IT Operations are no exception. Many companies are implementing a Distributed IT Operations Center (D-NOC) approach to address this new reality.

In this article: Infrastructure monitoring systems have been undergoing massive change in the past few years. Before the proliferation of cloud computing, IoT and edge computing, mobile apps and SaaS apps, the practice was fairly static, albeit traditionally quite siloed. IT managers needed to get data on a set of standard metrics, from a handful of tools.

You can utilize an SSL checker to troubleshoot the common SSL errors and vulnerabilities if you have installed an SSL certificate before. There is a plethora of tools you can choose from. You can also use a free SSL checker if you are working on a low budget. And using an SSL checker tool is quite simple. You simply must submit the domain name or IP address and the port number it requires to examine your website’s configuration and security.

Remote access to intranets and otherwise restricted areas was always a challenge. On one hand, it’s desirable to re-create convenient and familiar access to the same resources; on the other hand, there are many issues, starting from ensuring security and access reliability The same is related to monitoring. If a network’s devices should be monitored, there always should be access to them; thus, there’s a separate task of monitoring accessibility. Below are several guidelines.

“Remember that guy that gave up? Neither does anybody else.” Progress on the new Monitive has been slow as a snail in a marathon, but nevertheless the progress was there. Since the last update last year, a lot has been going on, and one day I woke up and just decided to write, even if small updates. Not only because Monitive is about transparency, but because I love writing.

Apache Flink is an open source framework, written in Java and Scala, for stateful processing of real-time and batch data streams. Flink offers robust libraries and layered APIs for building scalable, event-driven applications for data analytics, data processing, and more. You can run Flink as a standalone cluster or use infrastructure management technologies such as Mesos and Kubernetes.

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.