Aiven for Metrics, a Prometheus compatible solution powered by Thanos, is now generally available. Last month, we announced the early availability of Aiven for Metrics, and as of today it is generally available!

Organizations across the globe are seeing rapid growth in the technologies they use every day. And while the healthcare industry has always been slow to adopt, they are quickly starting to benefit from the role new technologies play in enhancing patient care and operational efficiency. However, one major setback for healthcare SMBs when investing in advanced technology is working out how they are going to keep up with cybersecurity, performance, and management of these IT solutions.

Businesses heavily rely on IT Service Management (ITSM) platforms to ensure the smooth functioning of critical services. While these platforms offer excellent incident management capabilities—tracking, organizing, and reporting incidents—they often fall short when it comes to fast, reliable resolution. Enter incident resolution automation, a game-changer in optimizing ITSM investments.

To understand the challenges facing modern IT teams in managing a diverse range of endpoints, one word that keeps coming up? Proliferation. Organizations are faced with a rapidly expanding ecosystem of network devices, tools and assets–some of which are so hidden from view that IT doesn’t even realize they exist.

As a straightforward definition, AI inference is the process of applying a pre-trained machine learning model to new, unseen data in order to generate predictions, classifications, or decisions. Unlike the training phase, where the model learns from a dataset, inference involves utilizing the learned patterns to analyze and interpret new inputs.

As many of you have already seen in our previous blog posts and our early beta release, we’re working on a new, independent notification module. Right now, we only offer three ready-made channels for sending notifications. Today, I want to show you how you can create your own channel and add it to the Icinga Notifications module. In this blog post, I’ll show you how to build a bridge to Telegram and send new notifications to a group chat.

Since ScienceLogic was founded in 2003, our goal has been to support our partners, including Managed Service Providers (MSPs), with solutions that help them and their clients gain unparalleled visibility into their IT environments. Our objective has always been to help these organizations bring order to complexity, turn inefficiencies into productivity, and, in the process, help service providers and the companies they serve exceed their business objectives.

Data growth is growing at an extraordinary pace, with a compound annual growth rate (CAGR) of 28% projected over the next few years. For organizations dealing with logs, metrics, and traces, this massive data expansion brings both opportunities and challenges. As data volumes soar, having flexibility in where you store and analyze it—whether in a SIEM, object storage, or other platforms—has become essential.

Even though I’m a Prometheus maintainer and work inside the Prometheus code, I found many of the details of PromQL, the Prometheus query language, obscure. Many times I would look something up, or go deep into the code to find out exactly what it did, only to forget it again the next month. So, trying to live up to my job title of Distinguished Engineer at Grafana Labs, I resolved to write the definitive guide: what really happens when I execute a PromQL query?

A few years ago, I had a play with HTTP logging added in ASP.NET Core 6. ASP.NET Core 8 introduced a set of additional configuration options that I believe are essential to make this feature usable. I will recap the details from the previous post below, but for more context, the first part of this series is here. In this post, I'll go through some of the changes introduced in HTTP logging since last. Before I jump into the improvements, let's recap how to set up HTTP logging.