Operations | Monitoring | ITSM | DevOps | Cloud

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.

At Oh Dear, we’re always looking for ways to make web monitoring easier and more efficient for our users. That’s why we’re excited to introduce Tag Notifications, a new feature that expands our notification options beyond site and team-level notifications.

Network monitoring continuously observes and manages the performance, availability, and security of a computer network to identify issues before they affect operations. As IT infrastructure grows more complex, network monitoring ensures your business stays online, whether dealing with on-premises or cloud environments. In hybrid or multi-cloud settings, having visibility across all systems is crucial to maintain seamless performance and prevent disruptions.

Redis is an in-memory data store used primarily as a quick-response database or an application cache. As an open-source NoSQL database, Redis handles data operations in microseconds, making it perfect for applications that need real-time processing. Fast, flexible, and easy to use, Redis has become a key player in modern application design.. Developers love Redis for its scalability and because it delivers application performance much faster than traditional databases, thanks to its in-memory operations.

Cyber threats are a major concern. Individuals, governments, and businesses all feel the impact. The emergence of advanced persistent threats is one of the most alarming forms of cyber espionage (APTs). These hacks are notable for their intricacy, tenacity, and broad penetration capabilities, whether they target a mobile or web application. APTs can harm the target network, including heightened geopolitical tensions, data theft, and protracted service interruptions.

Building applications using serverless technology on AWS—like AWS Lambda and Amazon API Gateway—can be incredibly powerful. You get to scale effortlessly and focus on writing code without worrying about managing servers. But as your application grows and spreads across hundreds or even thousands of cloud resources, keeping track of errors and fixing issues quickly becomes a big challenge.

In separate incidents this past month, I’ve helped clients troubleshoot network problems that turned out to be due to misconfigured switches. In all cases, the errors turned out to be things that I don’t think should ever have been changed from their default settings. So I thought it might be useful to have a brief discussion about how switches work and what features should or should not be used in normal office environments.