Audit and history
One list of what has happened on this installation: deploys, container actions, pipeline runs, access events and configuration changes, each with who did it, what it was done to, and when. It is the answer to "what is running is not what I expected - who changed it".
What a row holds
The day and time, the person or system that acted, the kind of event, the target it acted on, a sentence describing it, and any detail. Kinds include deploy, restart, stop, start, rollback, create, pipeline, VCS, runner, configuration, maintenance, access and notification results.
Filtering it
A search box matches the actor, the target and the text. Category tabs narrow it to Stacks, Containers, Pipelines, Access or Activity. The last three are the audit categories and appear on Team and above.
Exporting it
Export writes what is currently filtered - not just the page you are looking at - to a CSV file with one column per field, named for the day it was exported. It is generated in your browser from the rows already loaded. Export is part of Team and above.
How long it is kept
| Plan | History and metrics kept | Audit categories | CSV export |
|---|---|---|---|
| Community | 3 days | - | - |
| Personal | 7 days | - | - |
| Team | Unlimited | Yes | Yes |
| Max | Unlimited | Yes | Yes |
Where the window is configurable it is chosen on the page - 7, 30 or 90 days, or forever - and the automatic clean-up drops anything older each day.
Clearing it
Clear deletes the whole history permanently and asks for your account password to prove it is you. It removes the record of what happened; it does not touch stack versions or the ability to roll back.