Audit logs
Database audit logs expose supported management and editor actions. They are not a complete audit of every statement executed by native database clients.
Workspace members can read the database’s audit events. The API uses standard limit/offset pagination and optional exact-match filters action, user_id and resource_type. Use action values from returned records; do not assume another product’s event naming scheme.
Events include actor, action, resource identifiers, timestamps and details where recorded. Editor logging covers selected modification statements and Redis/MongoDB editor actions; its presence does not establish comprehensive statement capture. Failed or unlogged operations may need application logs and request IDs for diagnosis.
Record the database UUID, UTC time window and X-Request-ID when reporting a management issue. Redact secrets from payloads and query text. If your application needs comprehensive data-access auditing, design and verify it separately from the management log.