Releases Index

BetaWeekly digests are a beta — we're trying something new. Feedback welcome.

Agents move into the observability stack, and a CA cleanup sweeps the SDKs

October 19–25, 2026

AxiomSentryDash0Datadog
Axiom, Sentry, Dash0, Datadog

Axiom wired monitor alerts into Cursor and Claude Code, Sentry opened the beta of its next Python SDK major and gave its MCP server dataset-specific search tools, and a compromised eMudhra CA forced certificate-trust fixes across Datadog and Sentry.

The week at a glance

Replay the week
FeaturesEnhancementsFixesMajorLandmarkTile size reflects impact

Coding agents become first-class observers

Axiom's biggest week was about putting agents on both ends of the telemetry pipeline. Monitor alerts now ship to Cursor automations and Claude Code routines, so a monitor summary can land directly where an agent is already working, and monitor labels travel with those alerts to Slack, Teams, Discord, and webhooks. The same batch made the Axiom MCP server connectable through a copy-paste setup prompt in Claude Code, Codex, OpenCode, Devin Desktop, GitHub Copilot in VS Code, and Cursor, and added Cmd+F search across span names, services, and field paths inside the trace viewer. A day later Axiom highlighted the critical path in trace waterfalls, dimming off-path spans so a slow trace's real bottleneck stands out.

Sentry took the same idea to its data model. Its hosted MCP server replaced the catch-all search_events tool with dataset-specific search tools — errors, logs, traces, metrics, profiles, replays — so an agent picks the right corpus instead of guessing, runs log regex filters as written, and can call a new find_dropped_events tool to check whether Sentry received but discarded the spans, logs, metrics, or errors behind a chart.

Dash0, meanwhile, started scoring what those agents produce. Its beta Evals use an LLM as a judge on agent generations as spans arrive, with configurable triggers, span filters, sample rates, and numeric, boolean, or categorical verdicts that land in the span's Evals tab and as log records usable in dashboards and check rules.

Trust stores get a hard cleanup

One compromised certificate authority set the agenda for the week's security work. Datadog's Agent rejected TLS chains containing the compromised eMudhra intermediate keys, updated its data plane to reject the affected public keys on direct and proxied HTTPS including FIPS builds, and moved to the October Mozilla CA bundle; the 6.x line dropped the emSign roots from its embedded bundle and stopped chunking output from manual container and process checks. The Python interpreter inside the Agent now rejects those chains regardless of trust store, and on Windows no longer trusts them through the OS store.

Sentry's CLI made the same move in two places: its Docker image requires a ca-certificates build with the distrusted roots removed, and its Volta-pinned Node.js jumped to a release that distrusts the compromised keys. The other Sentry CLI update was a snapshot build with no reader-facing changes.

The Python and JavaScript SDKs shift underfoot

Sentry opened the beta of its next Python SDK major, slated for general release in November 2026 and collecting feedback in GitHub discussions — the time to test instrumentation against it is now. On the stable side, Sentry Python added cron and periodic-task monitoring for arq, Huey, and rq-scheduler, and stopped swallowing exceptions raised during Cohere and huggingface_hub stream iteration.

Sentry JavaScript shipped a breaking rename: several span origins were aligned with the other v11 names — auto.http.wintercg_fetch becomes auto.http.fetch, gRPC serverless becomes auto.grpc.google_cloud — so any ignoreSpans rule, query, or alert matching the old strings needs updating. Deno.serve integration now records request sessions and ignores static assets by default. On the Datadog side, dd-trace-py fixed google-adk 2.9 startup failures and a regression that force-finished open LLM spans at request teardown, plus vLLM and OpenAI Agent concurrency bugs.

Tooling churn: CLIs, dashboards, and traces

Across the two CLI families the week was mostly about ergonomics. Sentry's newer CLI gained feedback triage, replay downloads, and DSN listing and, a day earlier, batch issue commands, event attachment metadata, and a wasm-split port along with fixes for old traces and paged project lists. Dash0's CLI made --agent-mode win over its environment variable under a single flags-then-env-then-profile precedence order, and added experimental datasets behind a flag.

In the UI layer, Sentry's trace waterfall added time compression, pinned attributes, and clickable Web Vitals; Dash0 let you drag dashboards and saved views into folders and broke Agent0 credit spend down by source, consumer, and model. The Dash0 Operator added bad/total and raw SLO indicators and self-managed webhook certificates. Rounding out smaller items: the Datadog Agent added an unreliable-mount log profile and made log registry updates durable and stopped crashing on Apple M6 hosts; Datadog RUM stopped passing undefined arguments to fetch; and Sentry's scraps library fixed Vite and webpack theme imports and unclamped dropdowns in table headers.

AI-generated digests may contain mistakes.
Releases covered24
Sentry