Track every action across your team with a complete, tamper-proof event trail.
DataRaven records every meaningful action that happens within your team — whether triggered by a user, an API key, or the system itself. The audit log gives you full visibility into who did what, when, and from where.
User Actions
Every create, update, and delete performed through the dashboard or API.
System Events
Scheduled task executions, transfer completions, and failures — logged automatically.
Request Context
IP address, user agent, and request ID captured with every user-initiated event.
Narrow to a specific resource — tasks, executions, secrets, locations, members, notifications, or vault connections.
Actor type
Show only events from users, the system, or API keys.
Date range
Filter events to a specific time window.
You can export the current view to CSV for compliance reporting, incident investigation, or offline analysis. The export includes all fields: timestamp, event type, resource, actor, summary, IP address, user agent, and request ID.
Recorded across the full lifecycle of a transfer execution — from submission through completion or failure. Execution events come from both user actions and the system.
User-Triggered
System-Triggered
These events are initiated by a user through the dashboard or API and include full request context (IP, user agent, request ID).
Event Type
Summary Example
Metadata
execution_submitted
Submitted execution for task “Daily S3 Backup”
trigger (manual, api), is_dry_run
execution_cancelled
Cancelled execution for task “Daily S3 Backup”
—
These events are generated by background workers and scheduled jobs. They do not include request context.
Event Type
Summary Example
Metadata
execution_submitted
Submitted execution for task “Daily S3 Backup”
trigger: scheduled, is_dry_run: false
execution_started
Started execution for task “Daily S3 Backup”
—
execution_completed
Completed execution for task “Daily S3 Backup”
stats (transfer statistics), error
execution_failed
Failed execution for task “Daily S3 Backup”
stats, error (error message)
execution_pending
Pending execution for task “Daily S3 Backup”
stats, error
execution_running
Running execution for task “Daily S3 Backup”
stats, error
execution_dry_run_completed
Dry run completed for task “Daily S3 Backup”
stats, error
Scheduled task executions are logged with trigger: scheduled and actor name “Scheduled”, making it easy to distinguish automated runs from manual ones.
Recorded when cloud provider credentials are created, modified, or removed.
Event Type
Trigger
Summary Example
Metadata
secret_created
User
Created secret “Production AWS”
secret_type (e.g., aws_s3, azure_blob)
secret_updated
User
Updated secret “Production AWS”
updated_fields — list of changed fields (credentials excluded)
secret_deleted
User
Deleted secret “Production AWS”
—
For security, the updated_fields metadata for secret updates intentionally excludes the credentials field — you’ll see which fields changed, but credential values are never logged.
When a task has a cron schedule configured, DataRaven’s scheduler automatically submits executions at the defined intervals. These scheduled runs are fully tracked in the audit log:
execution_submitted is logged with trigger: scheduled and actor name “Scheduled”
execution_started, execution_completed, and execution_failed are logged as the execution progresses through its lifecycle
Transfer statistics (files transferred, bytes moved, errors) are captured in the stats metadata field on completion
This means you can audit the complete history of your automated transfers — when they ran, whether they succeeded, and how much data was moved — without any manual intervention.
