It was a quiet week by volume, with three vendors producing stories in the weekly collection. The most notable item is a return: Observe, the company Snowflake acquired, produced the first product news the collection has recorded for it since the acquisition, an AI agent observability offering heading to private preview. Grafana Labs and Dash0 spent the week on adoption blockers rather than headline features: a migration path for Alertmanager configurations, payment card redaction, and a billing forecast.

Observe Returns With Agent Observability

On September 22, Snowflake announced AI Agent Observability for Observe by Snowflake, coming soon to private preview, with a launch event on October 22. The offering centers on an optional OpenTelemetry-compliant SDK with tested support for LangChain, the Anthropic Agents SDK and the OpenAI Agents SDK. An Agent Explorer lets teams search and debug conversations across traces and sessions to inspect agent behavior and tool calls, online LLM-as-judge evaluations run against production traffic to flag hallucinations and quality problems, and latency, error, token usage and estimated cost signals are derived from agent traces. Snowflake adds that teams can correlate agent behavior with customer experience, resolution rates, conversion and revenue using its broader data platform.

Update #3 listed Observe as a gap: no public news since the acquisition, and a need to reappear before the quarter closed. It did, with a preview rather than a general release, and Snowflake's own blog is the only source in the weekly collection. The feature list also fits the cost theme of Update #7 and the pricing analysis: per-agent token and cost signals are becoming a standard part of agent observability, and Observe now says it will offer them too.

Grafana Adds a Migration Path for Alertmanager

Grafana's What's New page lists import of Alertmanager configuration into Grafana Alerting, available in public preview. Teams can bring an existing Prometheus or Mimir Alertmanager configuration across alongside their alert rules, including contact points, routing policies, templates, time intervals and inhibition rules. Grafana runs the imported configuration in a Mimir-compatible way, so notification behavior is preserved without changes to integration settings or templates. Grafana Cloud customers need to contact Support to enable it. Routing trees and templates tend to accumulate over years, so an importer that preserves behavior lowers a real switching cost for teams already running Prometheus-style alerting.

Dash0 Ships Compliance and Cost Visibility

On September 25, Dash0 released Cardholder Data Redaction, an opt-in dataset setting that masks payment card data in logs, spans, web events and metrics before Dash0 stores it. Card numbers keep their first six and last four digits, so a test number appears as 411111******1111, while verification codes, PIN blocks and track data are replaced entirely with <REDACTED>, which PCI DSS prohibits storing, according to Dash0's documentation. Detection is pattern-based: the documentation lists base64 or hex encoded, encrypted, tokenized, hashed and JSON-escaped numbers as undetected, along with cardholder names, expiry dates and service codes. The setting is off by default and needs the Maintainer role to change. Dash0 calls it a defense-in-depth control with documented gaps and offers no compliance guarantee.

Two days earlier, on September 23, a Forecast tab on the Billing & Plans page began projecting the cost of a full billing cycle. Dash0 takes a baseline window, scales its usage rate to a full cycle, and prices it against the organization's real pricing tiers and any custom prices, broken down by SKU and dataset, the way the invoice is calculated. That is a spend projection for the whole account, a different thing from estimating what a single agent task will cost before it runs, the gap described in the pricing analysis.

On September 21, Dash0 also added automation triggers from GitHub Actions workflows. Automations can fire on workflow runs, jobs, manual dispatches, check runs and check suites, scoped by organization, repository, branch or workflow name and filtered by conclusion or status. Dash0's example is an automation that picks up a failed run, works out why it broke, and pushes a fix so the workflow runs again. It extends the GitHub Action for syncing dashboards and check rules covered in Update #7.

What to Watch

CriblCon 26 opens in Chicago on September 29 and 30, with a campus day on September 28, and is the next scheduled source of platform announcements. Snowflake's launch event for Observe's agent observability is set for October 22. Dynatrace's $915M acquisition of Arize, announced on August 13, was still pending at the end of this period, and the company had said it expected to close later this quarter or early in its third quarter, subject to regulatory review.