Every significant action — from deployments to user management — is recorded with timestamps, user details, and context.
Overview
- Who did what, when, and where – every action is traceable.
- Logs include user identity, action type, resource affected, and timestamp.
- Useful for security investigations, compliance, and debugging issues.
What Gets Logged?
| Category | Example Actions |
|---|---|
| Deployments | Service deployed, redeployed, rebuilt |
| Scaling | Manual or autoscale events triggered |
| Configuration | Changes in DCDeploy.yml, env vars, or domains |
| Access Control | User invited, role updated, or removed |
| Billing & Plans | Plan upgraded/downgraded, payment attempts |
| Networking | Domain changes, TCP proxy setup, SSL updates |
Viewing Audit Logs
Dashboard
- Navigate to Organization → Audit Logs.
- Filter logs by:
- User
- Service
- Action type
- Date range
- Export logs in CSV or JSON for compliance reporting.
Use Cases
- Security – Detect unauthorized or suspicious activity.
- Compliance – Maintain audit trails for SOC2, GDPR, HIPAA, etc.
- Debugging – Trace who triggered a failed deployment or config change.
- Collaboration – See recent activity by team members.
Retention Policy
- Logs are stored for 90 days by default.
- Enterprise plans allow custom retention (up to 1 year).
- Export regularly if you need longer history.
Best Practices
- Assign proper roles & permissions to limit risky actions.
- Regularly review audit logs for anomalies.
- Enable alerts (via email or Discord integration) for critical events:
- Service deletions
- Billing changes
- User role escalations