Operations | Monitoring | ITSM | DevOps | Cloud

2025 has truly been the year of Agentic AI, with MCP (Model Context Protocol) emerging as one of its flashy and most talked-about innovations. While many products have seamlessly integrated MCP servers into their systems, these servers are increasingly being labelled as black boxes, opaque components that handle critical tasks but offer little visibility into what's happening under the hood. We prompt an agent, a tool gets invoked, and a response is generated. But what really happens in between?

Isn’t the "Bring Your Own Cloud" (BYOC) model the latest hot topic in the evolution of cloud-native architecture, especially for companies offering cloud-hosted platforms that must be deployed in the customer’s cloud for privacy, control, or compliance reasons? Over the past few weeks, we have been rigorously researching and discussing how to build a secure BYOC model.

Traces tell you what happened and when. Logs tell you why. When something breaks, logs are often your first clue—and if they’re correlated with traces, they can cut debugging time down from hours to minutes. In this section, we’ll wire up end-to-end structured logging across both server and browser environments in your Next.js app, complete with trace correlation and SigNoz integration.

Nextjs is a production-ready React framework for building single-page web applications. It enables you to build fast and user-friendly static websites, as well as web applications using Reactjs. Using OpenTelemetry Nextjs libraries, you can set up end-to-end tracing for your Nextjs applications. Nextjs has its own monitoring feature, but it is only limited to measuring the metrics like core web vitals and real-time analytics of the application.

In the fast-paced world of CI/CD, understanding the performance and behaviour of your pipelines is crucial. GitHub Actions has become a popular choice for automating builds and deployments, but anyone who's debugged a flaky workflow or long-running job knows how challenging it can be to get visibility into what's happening under the hood. We usually rely on build logs, timing data, or guesswork when something goes wrong.

Choosing the right APM tool is critical. How do you know which is the right one for you? Here are the top 13 open-source application performance monitoring(APM) tools that can solve your monitoring needs. Open-source APM tools have added benefits over their SaaS counterparts. They are more transparent, as you can verify their source code, and you can use them without going through the pains of obtaining approvals usually required for using a third-party vendor tool.

In one of our previous blogs, we discussed distributed tracing in depth. We examined why distributed tracing is critical and its components - spans and trace context. You can check the complete guide here: What is Distributed Tracing and How to Implement it with Open Source? Here, we'll look at some of the best distributed tracing tools. We'll see what each of them offers so that you can choose the right tool for your monitoring and observability requirements.

Node.js powers some of the fastest-growing web applications, but its single-threaded nature makes it vulnerable to memory leaks and CPU spikes. To keep your app running smoothly, especially in production, you need more than just web server logs — you need complete visibility across the entire stack.

Observability is essential for maintaining and scaling modern applications. With.NET 8, Microsoft has enhanced support for observability using OpenTelemetry. In this post, we explore how to monitor.NET 8 applications logs with SigNoz, an open-source observability platform, using the OpenTelemetry Protocol (OTLP) exporter.

‘One small step for a man, but a huge leap for developers’ — me, when I realised how to observe my Backstage with OpenTelemetry. Backstage is often the “portal” through which we manage all our other systems, but who watches the watcher? Recently, we gave a KubeCon Talk, highlighting that monitoring Backstage itself is critical. When Backstage isn’t observable, it becomes a blind spot in your infrastructure.