Skip to main content
Action logs provide an audit trail of administrative actions and configuration changes made within your Pangolin organization. These logs help you track who made what changes and when.
Make sure to enable access logs in the org settings

​
What are Action Logs?

Action logs capture administrative events and configuration changes performed by users or API keys in the Pangolin dashboard. They record management operations such as creating resources, modifying settings, managing users, and other organizational changes. These logs are useful for:
  • Maintaining an audit trail of configuration changes
  • Tracking administrative actions for compliance
  • Identifying who made specific changes to your infrastructure
  • Troubleshooting configuration issues by reviewing recent changes
  • Meeting security and compliance requirements

​
Action Log Fields

Each action log entry contains the following fields:
FieldTypeDescription
timestampnumberUnix timestamp (in seconds) when the action was performed
actionstringThe specific action that was performed (e.g., “createResource”, “updateUser”, “deleteTarget”)
actorTypestringThe type of actor performing the action (“user” or “apiKey”)
actorstringThe display name of the actor (username or API key name)
actorIdstringThe unique identifier for the actor (user ID or API key ID)
metadatastringAdditional contextual information about the action in JSON format (often contains request parameters)

​
Log Retention

Action log retention is controlled by the organization settings. By default, action logs are retained for 0 days (disabled).

​
Exporting

Logs can be exported into CSV format for external analysis and archival. Logs can be exported from the table view in the Pangolin dashboard or via the Pangolin API. When exporting, you can specify date ranges and filters to narrow down the logs you need.