Operations | Monitoring | ITSM | DevOps | Cloud

Control trace volume with OpenTelemetry tail-based sampling

OpenTelemetry (OTel) tail-based sampling helps teams control trace volume by retaining errors, slow requests, and other traces worth investigating while dropping lower-value traffic. In distributed systems, a single request can fan out across many services, each emitting spans. That volume adds up quickly. Some applications produce millions of traces per hour, while large clusters generate more than 10 billion spans per day.

GitHub Copilot Monitoring & Observability with OpenTelemetry

Learn how to implement end to end monitoring and observability for GitHub Copilot Chat using OpenTelemetry and SigNoz. In this video, we walk through enabling the OpenTelemetry exporter built into the Copilot Chat extension in VS Code, collecting a trace for every agent turn, and visualizing everything in SigNoz to gain real time visibility into model calls, tool executions, token usage, prompt cache savings, latency, and failures. Copilot Chat ships its own OTLP exporter, so there is no instrumentation library to install and no collector to run.

Grok Build Observability with OpenTelemetry

Learn how to implement end to end observability and monitoring for Grok Build, xAI's terminal coding agent, using OpenTelemetry and SigNoz. In this video, we walk through turning on Grok Build's native OpenTelemetry exporter, collecting metrics and structured session events, and visualizing everything in SigNoz to gain real time visibility into token usage, sessions and turns, tool calls and their outcomes, error categories, and startup latency. Grok Build ships its own exporter, so instrumenting it is a matter of configuration, with no library to install and no collector to run.

From alert to answer: a hands-on investigation with trace analysis in Mezmo

Authored by Sven Delmas, VP of Research at Mezmo I wanted to know what Mezmo's new trace features feel like with real telemetry behind them, so I built the smallest honest rig I could: the OpenTelemetry demo application running in a local Kubernetes-in-Docker cluster on my machine, one collector, and one deliberately simple Mezmo pipeline.

Debug AI agents wherever they run, from Slack bots to code review with Sentry's Agent Tracing

Agent Tracing shows the full execution path of an AI agent: the model call, every tool invocation and its arguments, token counts, cost, and the span where it broke. Same traces and spans you already use, with agent-specific attributes on top. Serge walks through three apps — a Next.js e-commerce agent using the AI SDK with a failing tool call, a Slack bot built with Eve that orders lunch, and a code review agent built with Flue over MCP.

We Redesigned the SigNoz Trace View for Million-Span Traces

A quick walkthrough of SigNoz Cloud's new trace detail view, with a flame graph that renders 100,000 spans in a single load. AI and agent workloads are producing traces with much higher span counts. We rebuilt the trace detail view in SigNoz Cloud to make investigating large traces faster. Here's what's new.

SigNoz Cloud Dashboard Schema Is Now Built for AI Agents

A quick walkthrough of SigNoz Cloud's new dashboard schema, redesigned to make dashboard operations by AI agents faster, more reliable, and lighter on tokens. AI agents are increasingly creating and editing observability dashboards. We redesigned the SigNoz Cloud dashboard data model with a structured, strictly validated schema so agents can work against defined fields and paths instead of inferring the dashboard structure.

OpenTelemetry at the edge: Observability for IoT fleets with Bindplane and Dynatrace

By the time an IoT device shows up in an incident review, it has usually already done its damage. Not the dashboard-gap kind. These devices are load bearing. They sit in the control path of substations, haul trucks, pump stations and cold rooms, so when they go blind the blast radius gets measured in tripped relays, spoiled stock, and unplanned outages rather than in missing datapoints.

Grafana Tempo: Trace diff & span pruning (August 2026 Community Call)

We will look at some new features: trace diff and span pruning Can't comment in the chat? You may need to create a channel. Join us live for an introduction to flame graphs. We’ll cover what they are, how to read them, and how to use them to find performance bottlenecks in your applications. Bring your questions! Grafana Cloud is the easiest way to get started with Grafana dashboards, metrics, logs, traces, and profiles. Our forever-free tier includes access to 10k metrics, 50GB logs, 50GB traces and more.

How to Reduce Data Costs with OpenTelemetry and Bindplane

Originally written by Paul Stefanski, updated by Dylan Myers. Data costs fill a large column in many organizations' accounting sheets. Data pipeline setup and management is a significant time sink for DevOps, IT, and SRE. Setting up telemetry pipelines to reduce unwanted data often takes even more time, which could better be spent creating value rather than reducing costs. This post will show you how to quickly set up your data pipeline to filter unnecessary telemetry data.

Your OTel spans, our errors: A Sentry love story in one trace

You can already send OTel traces to Sentry. Point your OTLP exporter at Sentry’s endpoint, set environment variables, and your spans show up in the trace explorer. Our OTLP setup guide and “You Don’t Need to Pick One” walk you through that. But those spans are islands. You get a trace waterfall in Sentry, sure.

Just ask AI to add OpenTelemetry to your code

OpenTelemetry instrumentation used to mean hours of manual work, wiring up metrics service by service. Now you can just ask for it. Tell an AI agent what you're trying to observe, something like "add OpenTelemetry so I can track this application's performance," and it turns that into an intent specification, then enriches your existing code with instrumentation to match. OpenTelemetry is open source and on GitHub. Pairing it with an AI agent that actually understands your codebase is what turns "add some metrics" into instrumentation that's useful.

How SigNoz MCP Helped MSI Find 20 Unnecessary Operations

Taylor Mattison explains how SigNoz MCP helped surface wasted work inside MSI's sales-order workflow. Warning checks were firing on user actions that had nothing to do with any warning they could raise. By comparing telemetry across the workflow, Taylor could point to unnecessary operations that were wasting API calls, database time, and server capacity. This clip is part of our MSI customer story on using SigNoz MCP with Claude to debug slow sales orders across the stack.