Operations | Monitoring | ITSM | DevOps | Cloud

Now more than ever, modern networks play a pivotal role in today’s business operations. However, this increased importance comes with a challenge: Modern networks are becoming increasingly complex and heterogeneous. Network managers need to ensure optimal performance across various domains—from the data center to multi-cloud and software-defined networks. This requires the consolidation of vast amounts of data from across multi-vendor networks, including environments managed by third parties.

In the fast-paced world of Kubernetes, guaranteeing optimal performance and reliability of underlying infrastructure is crucial, such as container and Kubernetes networking. One key aspect of achieving this is by effectively managing alerts and notifications. This blog post emphasizes the significance of configuring alerts in a Kubernetes environment, particularly for Calico Enterprise and Cloud, which provides Kubernetes workload networking, security, and observability.

As noted in my previous article Diving into JTAG protocol. Part 1 — Overview, JTAG was initially developed for testing integrated circuits and printed circuit boards. However, its potential for debugging was realized over time, and now JTAG has become the standard protocol for microcontroller debugging. Many Firmware and Embedded engineers first encountered it in this particular context.

The.NET programming language is taking cloud native deployment and observability seriously, and most notably with the recent announcement of.NET Aspire stack unveiled at the recent.NET Conf 2023. In the latest episode of OpenObservability Talks, we reviewed the journey to making.NET a “by default, out of the box observable platform,” as ASP.NET Core creator David Fowler put it.

Integration is a crucial aspect of modern IT service management. By linking their ITSM platform with external applications, businesses can simplify their IT operations, enhance efficiency and flexibility, and provide better customer service. Real-time integration allows businesses to quickly adapt to changing circumstances and ensure that IT services align with business requirements. However, ITSM integration can be complex and difficult.

TL;DR You deserve a better alerting and on-call tool. So we built Signals. In our early days, we often used the tagline, “You just got paged. Now what?” It encapsulated how FireHydrant solved for all of the messy bits that come after your alert is fired, from incident declaration all the way through to retrospective. At the time, we saw alerting and on-call scheduling as a solved problem.

SRE and IT Operations play a critical role in ensuring reliable, high-performance applications. Yet, SREs (Site Reliability Engineers) often face ‘thrown-over-the-wall’ code deployments to operate without having insights into the code-level features. In my previous article (“Is your Java Observability tool Lambda Expressions aware?”), I delved into one such code-level feature: Java lambda expressions which replace anonymous inner classes.

A few days ago, I challenged myself: Could I create a CPU throttling monitor without using StackState's docs page? I'll go a bit deeper into CPU throttling later, but first: Why this mission? At StackState, we believe that every software developer should be able to observe the health and reliability of their own application — quickly and easily.

In a recent interview with Ewan Cameron, the Product Manager behind N-central RMM, we got an exclusive insight into the groundbreaking features and improvements rolled out in the first release of N-central for 2024. So, let’s dive into the key highlights of N-central 2024.1.

In recent years, hybrid cloud environments have emerged as a popular, if not de facto, choice for many organizations seeking flexibility, scalability, and security in their IT infrastructure. Industry research firm Mordor Intelligence pegs hybrid cloud as a nearly $130bn market in 2024, growing at a better than 22% clip over the next five years.