---
agentTools:
  projectIndex: https://docs.observeinc.com/llms.txt
---

# 2026-09-02

# What's new this week

This section summarizes what was released this week.

## Fast lane GA features

These features are generally available for all customers. Slow lane customers and tenants will have these features automatically enabled on September 30, 2026.

* **ai-sre**: AI-assisted monitor creation now runs on the more capable Page mode AI, improving the quality and conversational flow of AI-guided monitor setup. Eliminates the rigid prompt-and-advisory-tools flow in favor of a more flexible, context-aware interaction that better handles complex monitor configurations.
* **monitors**: Monitor create and edit forms now include an optional missing-data alert expiration override, letting teams set a custom duration (up to 24 hours; default is 2 hours plus the lookback window) for how long a missing-data alert stays active before it auto-expires. Eliminates the need to manually close stale missing-data alerts after data resumes flowing.

## Slow lane GA features

These features are enabled for all slow lane customers and tenants today.

* **ai-sre**: AI-guided creation for threshold and anomaly monitors — including notification action editing — is now enabled for all slow-lane AI-SRE customers, completing its rollout to all tiers. Fast-lane GA was 2026-07-29.

## Public preview and private preview features

<button className="pill" style={{ backgroundColor: "#ffc107" }}>PrPr</button> features are available by invitation only. <button className="pill" style={{ backgroundColor: "#FF8C00" }}>PuPr</button> features are available by inquiry.

* <button className="pill" style={{ backgroundColor: "#ffc107" }}>PrPr</button> **navigation**: Simplified URL format is now enabled for selected customers — workspace path prefixes are no longer included in generated URLs. Legacy prefixed URLs continue to work.

## Bug fixes

The following issues are fixed in this week's release:

* **monitors**: Slack notification actions were missing the headline text in their message format. (OB-65753)
* **ai-sre**: Sensitive data — including AI data-extraction samples, monitor alarm values, and query results — is now properly redacted in AI query and monitor contexts. (OB-65908)
* **iceberg-catalog**: Multiple reliability fixes: metadata tables are now reachable, vended credential session expiry is correctly sent, failed fills are no longer served, and silent load-table retries no longer mask errors. (OB-65537, OB-65931, OB-65461, OB-64937)
* **worksheets**: Several worksheet export and v0-to-v2 pipeline converter fixes: expression builder and declared input split are restored after conversion, card inputs now read from the correct stage input list, and dataset filter types and parameter allow-empty flags are correctly preserved. (OB-65809, OB-65526, OB-65527, OB-65605, OB-65838)
* **filters**: Removing a correlation tag filter pill now correctly clears the filter. (OB-62884)
* **filters**: Tag equality filter pill values containing special characters are now correctly quoted. (OB-63295)
* **playground**: API Playground no longer includes an embedded bearer token alongside cookie credentials, preventing double-authentication failures. (OB-63432)
* **dashboard**: Default empty state is now sized to its content. (OB-65874)

## APM Tracing Content Rollout

The following APM tracing schema and content changes are rolling out this week.

### Non-breaking changes

* **service-metrics**: Service Edge Metrics are now sourced from Canonical Trace (previously Service Explorer Spans). Service Metrics have been restructured: a single `service_type` column (Service, Database, Message Broker, External) now replaces the independent `is_database` and `is_message_broker` boolean columns. New customers default to RED metrics generated by the agent instead of Tracing/Service Metrics.
* **service-explorer**: The `ModelMessageBrokerEntities` flag will be flipped on by default in the next scheduled breaking upgrade, modeling message brokers as first-class entities across Service Explorer.

### Breaking changes

*None.*

## REST API changes

The following changes are reflected in the [Observe REST API](https://developer.observeinc.com/) as of this release.

### New

* **Drop filters** — full CRUD for ingest drop filters is now available in the public API: `POST /v1/ingest/filters` (create), `GET /v1/ingest/filters` (list), `GET /v1/ingest/filters/{id}` (get), `PATCH /v1/ingest/filters/{id}` (update), `DELETE /v1/ingest/filters/{id}` (delete).
* **GET /v1/ingest/filters/filterable-datasets** (`ListFilterableDatasets`): Lists the datasets eligible for drop filtering.
* **POST /v1/ingest/filters/validate** (`ValidateIngestFilterExpression`): Validates a drop filter expression before saving it.
* `PrPr` **Ingest routes** — ingest route management endpoints are published as beta: `POST /v1/ingest/routes/{type}` (create), `GET /v1/ingest/routes/{type}` (list), `PATCH /v1/ingest/routes/{type}` (update priorities), `GET /v1/ingest/routes/{type}/{id}` (get), `PATCH /v1/ingest/routes/{type}/{id}` (update), `DELETE /v1/ingest/routes/{type}/{id}` (delete).

## Terraform provider

The following updates are available in the [Observe Terraform provider](https://registry.terraform.io/providers/observeinc/observe/latest).

### v0.14.67 (2026-08-28)

**Bug fixes**

* `query`: Stop perpetual plan diff from stage inputs no stage uses.
* `dataset`: Prevent perpetual diff from link-derived inputs.
* `dashboard`: Stop perpetual diff from stage input datasetId OID form.
* Warn when a dataset pipeline stage has no effect.
* Fix perpetual diff when stage input names the preceding stage's alias.

# Coming soon

The following GA features are already available for fast lane customers, and will be enabled for slow lane customers and tenants next week.

* **tags**: Global tag management — create and manage tags across datasets, monitors, and dashboards from a central tags page.
* **ai-sre**: MCP settings page, CLI install instructions, and native o11y agent API tools.
* **datasets**: Real-time (p90) freshness in dataset headers and the REST API, with goal-relative staleness reason reporting.