live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent
nl2sql.ai
newsEnterprise AI

Observe makes AI-SRE’s execution identity a monitor-level control

A new GA control shows whose account an investigation uses and lets operators reassign it; the same release also closes a cross-tenant read flaw.

Observe AI-SRE release timeline with identity control, security fix, and rollout dates.
Timeline: dates from the story
By The News Desk· Sep 17, 2026the quick take — two AI hosts go live when you do

Observe has added a small but consequential control to AI-SRE: the monitor form now shows whose identity an investigation runs under, and a monitor editor can claim that identity for themselves. The AI-SRE chatbot can also reassign it. Observe says the change makes clear which connectors and tools the investigation will use and lets users reclaim ownership without engineering help. The feature entered fast-lane general availability on September 16; slow-lane tenants are scheduled to receive it automatically on October 14. Observe changelog, Sept. 16

Why the identity label matters

For an investigation agent, “who is running this?” is not just attribution. Observe explicitly ties the displayed identity to the connectors and tools available during the investigation. That gives operators a visible place to check the authority behind an automated run before treating its output as routine monitor behavior. Reassignment also turns an otherwise implicit dependency on a user account into an editable monitor setting. Observe changelog, Sept. 16

The practical rollout check is straightforward: open each AI-SRE-enabled monitor, record the displayed identity, verify that its connector access is still intended, and assign a durable owner before a user changes role or leaves. Teams should also test reassignment in a non-production monitor and confirm what appears in their audit trail. Observe’s release note does not describe the audit event, credential-refresh behavior or what happens to an in-flight investigation when ownership changes, so those remain questions for tenant-specific validation. Observe changelog, Sept. 16

The same release underlines the boundary

Observe’s September 16 notes also disclose a fixed cross-tenant data-leak bug. A REST read against reference tables or a GraphQL read against monitors could return another customer’s data if a caller guessed or reused a cluster-global numeric ID. The company lists the issue as fixed, but does not state the affected versions, exploitation status or whether customers need to rotate credentials. Observe changelog, Sept. 16

The two changes are separate, but they point to the same operational lesson: agent behavior is bounded by both the identity attached to the workflow and the authorization checks on every data path it can reach. A visible owner is useful only if teams verify that the underlying connectors and APIs enforce the same boundary.

The release also moves AI-SRE in the trace inspector and natural-language semantic search over datasets to slow-lane GA, extending the surfaces where those access checks matter. Observe changelog, Sept. 16

sources

Filed by The News Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk