Observability is one of the busiest categories in the API Evangelist network, and the week of May 4-8, 2026 was no exception — 14 stories worth tracking, ranging from agent-runtime monitoring to cloud-cost analytics, FedRAMP certifications, and the long-running grievance that most cloud-native teams still run three observability stacks. The shape of the conversation has shifted: vendors are explicitly framing their products around “observability for AI” rather than just observability, and the OpenTelemetry standard is winning enough that it shows up across nearly every vendor.
This roundup organizes the week into four themes — agent-and-AI-specific observability, the OpenTelemetry standardization wave, the major-vendor moves, and the database-and-data-store observability subspace.
1. Observability for the Agent Runtime
Agent-specific monitoring is its own subspace now, with vendors shipping integrations targeted at the Claude Agent SDK, AI workloads, and the AI-driven inquiry experience.
- SignOz — Claude Agent SDK Monitoring & Observability with OpenTelemetry. First-class Claude Agent SDK monitoring through OpenTelemetry — the right plumbing.
- New Relic — Observability Drives the Success of Modern AI. The vendor framing: AI without observability is hope-driven engineering.
- New Relic — Introducing New Relic Knowledge: AI-driven insights grounded in your business context. AI-driven query/insight surface inside the observability product.
- The New Stack / Elastic — Elastic architects reveal how to query observability data in plain English. Natural-language querying of observability data. The interface convergence between observability and conversational AI is happening fast.
2. The OpenTelemetry Standardization Wave
OpenTelemetry has won, and the integration content reflects that.
- SignOz — Python OpenTelemetry Instrumentation.
- SignOz — Instrumenting a Temporal TypeScript application with OpenTelemetry.
- SignOz — Getting Temporal Cloud Metrics into SigNoz.
SignOz publishing this volume of OpenTelemetry integration content suggests they are positioning to be the canonical reference open-source observability stack on top of OTel.
3. Major-Vendor Moves
The big observability vendors did meaningful repositioning this week.
- Datadog — Datadog for Government achieves FedRAMP® High certification. FedRAMP High opens federal contracts. A meaningful business move.
- Datadog — Analyze cloud costs with flexible spreadsheets in Datadog Sheets. Cost management as a first-class observability concern, with a UI shaped for finance teams.
- Datadog — Inside Datadog’s AI Research Lab: Meet two PhD candidates behind Toto. Recruiting/research storytelling — useful for the talent narrative, not the buyer narrative.
- Snowflake — Observe by Snowflake: AI-Powered Observability at Scale for the Data Cloud. Snowflake adding AI observability to the data cloud. Different segment from Datadog, but same convergence.
- Atlassian — Introducing new AIOps integrations with Lansweeper, Coralogix, and Honeycomb. AIOps integration cluster.
- Sentry — Fixing JavaScript observability, one library at a time. Sentry doing the patient unsexy work in the JavaScript ecosystem.
4. Database and Data-Store Observability
Database observability is a subspace getting first-class treatment.
- Datadog — Diagnose and resolve database performance issues faster with Database Investigator. Database-specific observability tooling.
- Datadog — Monitor and optimize Supabase query performance with Datadog Database Monitoring. Specific Supabase integration.
- ClickHouse — Goodbye limitations, hello data: How Qonto is rethinking observability with ClickHouse Cloud. A reference customer (Qonto) using ClickHouse for observability — a different bet than the SaaS observability stack.
- SolarWinds — Database Observability: Faster Root Cause Analysis Starts With Better UX. The UX angle on database observability — usually under-discussed.
What This Signals For the Network
Three takeaways from this week’s observability coverage:
- Observability has absorbed the AI conversation. Every major vendor reframed something around AI this week — New Relic Knowledge, Datadog AI Research Lab, Snowflake Observe, Elastic natural-language querying, SignOz Claude Agent SDK monitoring. The category is no longer “observability that happens to also see AI workloads” — it is observability designed for them.
- OpenTelemetry has effectively won the instrumentation layer. SignOz publishing 3+ OTel integration posts in a week, plus every major vendor’s content presupposing OTel, is the standardization signal. Organizations not yet on OTel are now on the wrong side of the standardization curve.
- The “three observability stacks” problem is admitted. The CNCF noted this week that most cloud-native teams still run three. The tools have converged enough that this is now a process problem more than a tooling problem — and it is going to take vendor + ops cooperation to actually consolidate.
We are tracking the observability layer of every provider in the api-evangelist network on apis.io. If you are publishing observability tooling for APIs, agents, or data we should know — apis.io is where we index the operational surface of the API economy.