Audit logs are currently available in private preview. Contact your Orb representative to enable this feature for your account.
What audit logs capture
Each audit log entry records detailed information about an action performed in Orb:| Field | Description |
|---|---|
| Action | The specific operation performed (e.g., customer.created, subscription.cancelled) |
| Occurred at | Timestamp of when the action took place |
| Actor | Who performed the action, including their type (e.g., api_key, user) and identifier |
| Targets | The resources affected by the action (e.g., customer ID, subscription ID) |
| Context | Request metadata including IP address and user agent |
| Environment | Whether the action occurred in live mode or test mode |
Tracked actions
Audit logs are generated for:- Authentication events: User logins and provisioning events
- Write operations: Create, update, and delete actions across core Orb resources including customers, subscriptions, invoices, plans, and metrics
Sample audit log event
Data privacy
Audit logs capture metadata about actions, not the content of those actions. Specifically, API request and response bodies are not included in audit log entries. This ensures sensitive customer data remains protected while still providing a complete audit trail of operations.SIEM integration
Audit logs can be streamed in real-time to your Security Information and Event Management (SIEM) provider of choice. This allows you to:- Centralize security monitoring across all your systems
- Set up alerts for suspicious activity
- Correlate Orb events with other security data
- Meet compliance requirements for log aggregation