Operations | Monitoring | ITSM | DevOps | Cloud

When your system shows a "no healthy upstream" error, it usually means your load balancer can't connect to any of your backend servers. Let's get straight to fixing this problem.

A load balancer, also known as Global Server Load Balancing (GSLB), is the method of splitting and distributing the incoming network traffic to multiple hosts—which can be located at different geo locations—within the organization network. This helps the network effectively manage network traffic and prevent any delays in network services. With load balancing enabled in the hosts, the organization’s network services are faster and provide more reliable responses to clients.

Understanding the cost of Azure resources at a granular level is critical for managing budgets effectively. With resources deployed across different resource groups-be it by teams, departments, or projects-tracking expenses can become complex. By analyzing costs per resource group, organizations can allocate ownership, identify cost spikes, and ensure accountability.

In my previous blog, we ran through what NIS2 is and who it applies to. In this second part of the series, I’ll break down the main requirements you’ll find in NIS2 and help translate them into actionable and practical measures you can take to achieve NIS2 compliance. Join me in this post and start understanding what NIS2 is all about.

Even with the best monitoring in place, outages are unavoidable. Complex, modern IT environments rely on multiple third-party services, including critical cloud and API providers, and when any one of those goes down, it can trigger a domino effect of increased error rates and latency spikes across your system. And, because you don’t have as much visibility into external services, it can be difficult to identify that the problem is due to an outside outage or disrupted service.

In today’s complex IT landscape, network automation is no longer a luxury—it’s essential. This guide will help IT leaders understand the market for network automation tools, the key considerations for choosing a platform, and how these tools are redefining network management from day 0 to the far future. But first, let’s examine some quick network automation history to help us better understand what the future holds!

Amazon S3 is a leading object storage service, but its pricing model, particularly for data egress, often becomes a significant burden for businesses with high outbound data needs. Cloudflare R2, a relatively new option, offers an attractive alternative with its simplified pricing and performance benefits. In this blog, we will explore why you should consider moving from AWS S3 to Cloudflare R2, compare their pricing with real-world examples, and provide a step-by-step migration guide with Node.js code.

APIs (Application Programming Interfaces) are the foundation of applications, facilitating communication between different services. To authenticate and secure these interactions, API keys and tokens play a vital role. However, improperly managing these sensitive credentials can lead to security vulnerabilities. In this blog, we will explore what API keys and tokens are, how to securely manage them, and best practices to use them across services while avoiding exposure.

In this post we will take a look at the icingadb check command built into Icinga 2 for monitoring the health of Icinga DB. If you have already configured it, this blog post will give you some insights on what it actually checks, otherwise, it showcases what useful health checks you are missing out on and should serve as a motivation to enable the check.

APM is foundational in assessing an application's internal health. It employs a variety of tools and techniques to monitor crucial metrics such as response times, error rates, and resource utilization. This comprehensive analysis enables teams to identify bottlenecks, slow database queries, and other potential performance-related issues that could diminish the user experience.