AgentOps Center: Observability for Multi-Agent AI

Zusammenfassung

Pixel shares an analysis of AgentOps Center, a GitHub hackathon project for observing multi-agent workflows with OpenTelemetry and SigNoz. It explains how agent, model, and tool spans connect in traces to reveal loops, rate limits, latency, and costs, while noting the project’s limitations and unverified claims.

DEV Community

AgentOps Center: running multi-agent systems with OpenTelemetry and SigNoz

A multi-agent workflow takes 45 seconds to answer, no exception was thrown, and every dashboard is green. What do you do next? That operations question is what AgentOps Center sets out to answer. It is a small GitHub project built for a SigNoz hackathon. I read it file by file without deploying it, so this article keeps three things apart: what the code does, what the README claims, and what I could not check. The repository is more useful as a pattern than as a product. It shows how to name spans in a system of cooperating agents, where to send them, and how to make an assistant’s answer depend on real telemetry. We will walk through those three decisions, then the limits. A note on method: the last commit I read is dated 26 July 2026. I quote no star count because I did not read one from the source. The README says MIT, yet I found no LICENSE file in the tree, so check before reusing anything. The problem AgentOps Center targets: slow is not broken Classic APM counts requests and HTTP errors. An agent workflow behaves differently. It loops, replays a tool, or waits on a model provider that is rate limiting it. Nothing breaks, everything slows down, and the token bill climbs. The README lists the questions operators need to settle: which node looped, which tool returned a rate limit, what each sub-agent cost. Answering them takes spans per agent, per model call and per tool, all linked in one trace. That is what the code builds. Decision 1: how to name spans in a multi-agent system The file backend/instrumentation/agent_spans.py declares attribute constants. It reuses the gen_ai. keys for model calls, then adds house keys for agents and tools. The split is sensible. Standard keys let you compare models and providers, while house keys carry business logic: which agent, which workflow. A workflow identifier on every span then groups everything together, even when the spans come from different libraries. To see what a span carries, read the anatomy of an OpenTelemetry span. Two cautions apply: The OpenTelemetry GenAI conventions are moving quickly. The specification page now points to a dedicated repository that I could not read (the server returned an error when I checked). gen_ai.system may have been replaced by a newer provider attribute: unverified. gen_ai.usage.cost_usd is the project’s own invention, not a key I know to be standard. Dashboards built on it will stay specific to your code. One more design detail: gen_ai.prompt and gen_ai.completion are cut to 500 characters. Full prompts in spans are expensive and expose data, so truncation is a fair compromise. Still, set your own policy before production. See also OpenTelemetry attributes in Dynatrace. Decision 2: where the telemetry goes The setup.py module creates a tracer provider and a meter provider, exporting over OTLP gRPC to localhost:4317 by default, which OTEL_EXPORTER_OTLP_ENDPOINT overrides. It turns on FastAPI and httpx instrumentation, plus LangChain through OpenInference, which also covers LangGraph according to a code comment. Sampling is fixed at 100 %, flagged in the code as a demo setting. The repository’s Collector receives OTLP and writes straight to ClickHouse using SigNoz exporters, one pipeline per signal. This layout is for self-hosted SigNoz. With another backend, Dynatrace for instance, only the exporter changes: the OTLP protocol and the attributes stay. Our OpenTelemetry Collector to Dynatrace guide shows that variant. I have not tested this repository against Dynatrace. For operations, note the memory_limiter and the batch of 10,000 items every 10 seconds. Good instinct: an agent system can emit thousands of spans per run. The README’s smoke tests report between 2,340 and 3,559 spans per run. Decision 3: let an assistant diagnose, but only from evidence This is the most interesting idea. The Root Cause Copilot does not ask a model cold. An evidence engine first calls the SigNoz MCP server to fetch traces, error logs, metrics and alerts. I...
AgentOps Center: Observability for Multi-Agent AI
Powered by Readybot.io*

Das Neueste von Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …