Audit logs
Audit logs are the operational record for sensitive admin actions.
They are especially useful for:
- incident review
- change accountability
- collaboration in teams with multiple editors
Parameter share-link creation and revocation are explicitly documented as audit-log events.
Why audit logs matter
Section titled “Why audit logs matter”Audit logs help answer questions that always come up during incidents and reviews:
- who changed this?
- when did it happen?
- was the change intentional?
- what else changed around the same time?
That makes them useful for both engineering and operational workflows.
Useful audit scenarios
Section titled “Useful audit scenarios”- a feature flag was flipped and behavior changed unexpectedly
- a production parameter was edited during an incident
- a temporary share link was created for a teammate
- a team needs to review operational changes after a release
Where to view them
Section titled “Where to view them”In admin:
- sign in
- open
Audit Logsfrom the sidebar - use
Filter audit trail...to search by actor, target, or project - use the
Action TypeandEnvironmentfilters to narrow the list - click a row to open the details drawer
- use
Export Logsto download CSV or JSON
The audit log page is the main operator workflow here. The repo does not currently expose a dedicated top-level CLI command for browsing audit logs.
What you can expect to see
Section titled “What you can expect to see”The backend and admin code currently wire audit logging around actions such as:
- project creation
- user invitation and user changes
- environment creation and deletion
- parameter creation, update, deletion, and rollback
- parameter share-link creation and revocation
That means audit logs are not just a security extra. They are part of the normal runtime operations story.
What audit logs support
Section titled “What audit logs support”Even when rollback solves the immediate issue, audit logs help with the follow-up work:
- documenting the timeline
- understanding operator actions
- improving runbooks
- reducing repeated mistakes
Where they matter most
Section titled “Where they matter most”Audit logs are especially useful around:
- production feature flags
- incident-driven parameter changes
- temporary share-link usage
- team environments with more than one editor
Practical review flow
Section titled “Practical review flow”When something changes unexpectedly in production:
- open
Audit Logs - filter to the relevant environment
- search for the key, project, or teammate involved
- open the matching row
- compare the audit event with the parameter history on the project page
- roll back the parameter if needed
What kinds of actions appear in audit logs?
Section titled “What kinds of actions appear in audit logs?”The current repo wires audit logging around important admin actions such as project, user, environment, parameter, and share-link changes.
Are audit logs only for security reviews?
Section titled “Are audit logs only for security reviews?”No.
They are also part of normal operational workflows such as incident review, production change tracking, and collaboration across multiple operators.
Should I check audit logs after a rollback?
Section titled “Should I check audit logs after a rollback?”Often yes.
Rollback handles the immediate recovery, but audit logs help you understand the timeline and the operator actions around the event.
Why do parameter share links matter in audit logs?
Section titled “Why do parameter share links matter in audit logs?”Because share-link creation and revocation are sensitive collaboration actions and should remain visible in the operational record.