Operations | Monitoring | ITSM | DevOps | Cloud

API gateways are often viewed as the centralized entry point for client HTTP requests in a distributed system. They act as intermediaries between clients and backend services, managing API request routing, load balancing, rate limiting, access control, and traffic shaping across multiple backend services. This API management is vital for many services and products, but many organizations can put too much stock in it.

The industry is rapidly moving towards deeper AI integration than ever before. What was once simply focused on chatbots or recommendation engines has pivoted significantly to AI systems communicating with other AI systems. These AI tools are leveraging multi-agent workflows to accomplish complex tasks that traditional systems have struggled with. Innovation without validation is a liability. Any developer worth their salt will know that these systems require ample testability and validation.

Kubernetes has become the backbone of many modern application deployment pipelines, and for good reason as a container orchestration platform, Kubernetes automates the scaling, deployment, and management of workloads, allowing developers to make their applications easier to manage and deploy at scale without worrying about their service’s dependencies, their user’s operating system, or the intricacies of their data center or infrastructure provider.

If you’ve spent any time building cloud-native systems, you’ve probably tripped over the tricky beast that is gRPC streaming. It’s powerful, flexible, and feels like magic when it works. But the minute you need to test it? Suddenly, you’re in “hold my coffee, I need a week” territory. One of the most common places we see gRPC streams in the wild is when clients connect to asynchronous message buses like Google Pub/Sub.

Console Connect has become the first platform to be certified under Mplify’s (formerly MEF) expanded Lifecycle Service Orchestration (LSO) API Certification Program. The certification recognises Console Connect’s achievement in validating four of Mplify’s key LSO Business APIs – Address Validation, Quote, Product Order, and Product Inventory – ensuring they meet strict standards for conformance and interoperability.

Today, we are going to take a look at the Icinga 2 API and the various ways targets can be specified for different actions, such as querying information or scheduling downtimes. This post focuses on the API request payloads themselves and assumes some familiarity with sending requests to the Icinga 2 API. Please refer to our documentation for the missing details if you want to try the requests yourself. In general, specifying the objects to which an action applies works the same way for all actions.

Traditional performance testing often comes late in the delivery cycle, typically just before release. By then, performance issues are usually quite expensive to fix, can delay deployments, and frustrate development velocity. A Shift Left testing approach addresses this by integrating performance testing early in the development cycle so issues surface while they’re still easy and cheap to fix.

Are you interested in learning about API monitoring? Then you’ve come to the right article. Below, we explain what APIs are and why they’re valuable, explore the basics of API monitoring, and wrap up with practical advice on how to get comprehensive API monitoring in your organization.

Service level agreements (SLAs) are the contractual backbone between customers and technology vendors, outlining expected service availability, performance metrics, and remedies like service credits when service providers fail to meet agreed-upon service levels. This service agreement assures both the technical quality as well as the service quality of the services provided, and underpins the value perspective of the client.