Operations | Monitoring | ITSM | DevOps | Cloud

Learn how to set up browser checks using Grafana Cloud Synthetic Monitoring. In this video, we walk through how to create a browser check and analyze test results. Browser checks simulate real user interactions to track critical workflows and catch issues early.

Build funnels directly on your traces and get instant answers to questions like: What fraction of spans made it from event A to event B? Between which spans are most requests failing? What is the latency between key spans? Traditional observability tools let you inspect traces and spans, but they can’t aggregate or analyze how requests flow across multiple services or stages in your system. In asynchronous, distributed architectures, the root span rarely tells the full story-and there’s no way to measure conversion, drop-off, or latency between arbitrary steps across all traces.

Most teams have strong monitoring for production, but what about the journey before your code gets deployed? The CI/CD pipeline is where bottlenecks, flaky tests, and process gaps silently waste your team’s time. Until now, this part of the workflow has mostly been a black box. We’re excited to announce CI/CD Observability in SigNoz - a new way to track, analyze, and improve your software delivery process, powered by OpenTelemetry.

Ever tried to build a metrics dashboard and thought, “Wait, what metrics am I actually sending?” We heard this from users again and again-so we built Metrics Explorer. For the first time, you get a real-time, interactive view of every metric coming into your system: Whether you’re onboarding a new integration, debugging an alert, or just exploring your data, Metrics Explorer makes it easy to understand and work with your metrics-no more guesswork, just clarity.

Is it the third-party API or my code? Your service suddenly slows down, or errors spike, and you’re stuck guessing if it’s your own logic or an external API you don’t control. We’ve seen this pain across teams: dashboards don’t tell you which vendor or endpoint is the culprit, and debugging turns into a maze of guesswork. Rate limiting, vendor errors, or integration issues often slip through until users complain.