Monitoring your on-premise or hybrid infrastructure means keeping track of potentially thousands of devices, any one of which could be a point of failure. Additionally, silos between application and network teams can create visibility gaps that complicate troubleshooting. For network engineers investigating bottlenecks, being able to view real-time infrastructure health and performance data alongside application metrics is essential for ensuring their organizations meet key SLOs.

On Tuesday, June 7, internet users in numerous countries from East Africa to the Middle East to South Asia experienced an hours-long degradation in service due to an outage at one of the internet’s most critical chokepoints: Egypt. Beginning at approximately 12:25 UTC, multiple submarine cables connecting Europe and Asia experienced outages lasting over four hours. As I show below, the impacts were visible in various types of internet measurement data to the affected countries.

HAProxy Kubernetes Ingress Controller provides custom resources named Backend, Defaults, and Global that let you manage ingress controller settings more efficiently. To start using them right away, check the documentation for steps and examples. In this blog post, you’ll learn why custom resources are such a powerful feature and see tips for getting the most out of them.

I often hear from customers who complain about how “classic” performance testing (i.e., end-to-end testing with high volume of virtual users) of their applications before release slows down the cycle time by several weeks. In addition, the testing significantly consumes both people and infrastructure (hardware and software license) resources.