Operations | Monitoring | ITSM | DevOps | Cloud

Modern VMware Monitoring. Native to SCOM. Built for Scale.

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.

APAC customers have high expectations around instant payments, open banking, and mobile-first experiences. In March 2025, India’s real-time payment system, UPI went down for five hours. Millions experienced payment failures, failed fund transfers, and login errors and many vented their frustrations on social media. With banking and payment disruptions on the rise, regulators are calling for proof of resilience.

Monitoring your websites from the US region is critical for serving users from the US as it helps you improve website performance and compliance-related practices, ensure business continuity, and offer a better customer experience. Just a few milliseconds of added lag specific to US connections can impact bounce rates and conversions, making localized monitoring essential.

LangChain has become one of the most popular frameworks for building LLM-powered applications, making it easier to create agents that can reason, plan, and take actions. But like any production-grade AI app, LangChain agents can run into performance bottlenecks, hallucinations, or tool call failures. And without proper LangChain observability, it’s hard to know where things break down.

In Part 1 of this series, we explored how to instrument a LangChain trip planner agent with OpenTelemetry and send telemetry data to SigNoz. By tracing each step of the planning process: LLM reasoning, tool calls for flights, hotels, weather, and activities, and the final itinerary response, we saw how observability turns a black-box agent workflow into a transparent, debuggable system.

If you’ve ever worked in a loud office, you know the drill: A co-worker’s on a call, someone’s talking about the next Taylor Swift album in the break room, another’s constantly clearing their throat, and the HVAC sounds like a jet engine. It’s loud. Your brain tries to filter it all out, but it’s no use. Then you put on noise-canceling headphones… and suddenly, you can think again.

If you're like me, you got into this business because you love building awesome apps. If you've been in the development space long enough, you'll eventually have to do work on those awesome apps that doesn't feel so awesome. Security can be one of those things. Taking Rails security seriously is important, even though the Rails framework does much of the heavy lifting. Before we get too deep into the details of Ruby on Rails security, let's take a second to reflect on the good times. ...

The Elasticsearch storage engine team has made significant strides in improving storage efficiency and performance in Elasticsearch 8.19 and 9.1. Now that these changes are available, what impact can they have on your business? And how do you make the most of them?

Imagine you’re a frontend engineer monitoring the user experience for an e-commerce app. You notice your checkout flow has a 15% abandonment rate. Your API responses are inconsistent. Your users are frustrated, and you’re drowning in data and complex queries trying to figure out why. Sound familiar? You can use real user monitoring (RUM) to determine what has happened, looking at page load times, error counts, user sessions, etc.