Core Concepts

Observability and Auditing

Inspect tool execution and control how organization audit events are retained.

Observability and auditing

DataFuse exposes execution status and organization audit history so operators can understand what an agent attempted and whether the action completed.

Execution information

Depending on the route and provider, execution surfaces may include the selected integration, tool name, status, timing, and a sanitized error message.

Secret-aware errors

The playground replaces known credential values in error strings with [redacted]. Applications should still avoid sending sensitive provider payloads to logs unless they have an explicit retention and access policy.

Zero-retention audit mode

An organization can enable zero-retention behavior for organization audit events. When enabled:

  1. DataFuse prepares the audit event.
  2. If a webhook is configured, DataFuse attempts to forward the event.
  3. The event is not inserted into the DataFuse audit table.

This setting does not by itself guarantee that provider payloads, infrastructure logs, proxies, or external webhook destinations retain no data. Evaluate those systems separately.