Audit Logs
Less wondering.
More knowing.
Audit Logs
Investigate a configuration change
Narrow the log to a resource and inspect the request that updated it.
Start with the service or rule you are investigating. Narrow the time window, find the update and read the request that was submitted.
- Filter by search, date, action and resource.
- See the actor and time alongside the change.
Actor, time and the submitted change, kept together.
Audit Logs
Review administrative access
Follow user invitations, role changes and removals in one place.
Keep the history of your team's administrative access in one place. Invitations, role changes and removals tell you how that access changed over time.
- Identify the user or key behind an action.
- Inspect the affected resource in each entry.
Actor, time and the submitted change, kept together.
Audit Logs
Bring records into your tools
Retrieve entries over the API for your own archive or reporting workflow.
Bring administrative records into the reporting or archive workflow you already use. The API gives your tools a way to retrieve the log.
- Authenticate with an API key and organization ID.
- Choose a plan with retention that fits your workflow.
FREQUENTLY ASKED QUESTIONS
A few things you might be wondering.
Does this include connection or traffic logs?
No. These are administrative audit logs from the control plane. They do not record network connections, browsing or packet contents.
Can I retrieve the log programmatically?
Yes. Use GET /v1/audit-log with an API key and the required organization and content-type headers. Build your own archive or reporting integration around the response.
How far back can I look?
Audit log retention depends on your plan. Check the plan comparison on the pricing page before planning your retention workflow.
A LITTLE MORE YOU CAN DO
TRY IT ON YOUR OWN NETWORK
Connect your first two machines.
Install Baseguard, join the same organization, and put it to work.