Audit · Plans and data
Limits
A package sets how many events a month it covers and how long events are kept. Audit never turns an event away for a limit.
Limits by package
Loading the limits…
Events a month
Each event Audit adds to a project's log counts once, in the calendar month (UTC) it arrives in. A duplicate or a refused event doesn't count. The count starts again on the 1st.
Past the package's number, events are still kept, as always: an audit record must not be lost. The month is shown as over at the foot of Audit's menu and in the project's Settings, and the project's admins get one email the first time it goes over in a month. A bigger package is on the workspace's Subscription page at id.
Months events are kept
In the project's Settings in Audit, Keeping sets how many months its events are kept, from 1 up to the package's most. Every night, whole sealed days older than that are removed, with their seals kept, so the log still checks as whole (Old events).
Moving to a package that keeps fewer months brings the setting down with it, and the older days go the next night. Before you change it, export what you must keep longer.
The same on every package
| What | At most |
|---|---|
| Events in one request | 500 |
| One request's size | 2 MB as sent, 8 MB unpacked |
| Requests | 600 a minute per server secret |
| An event's context | 4 levels deep, 8 KB as JSON |
| An action | 80 characters |
| A target's kind | 40 characters |
| An id | 64 characters |
| A reason | 500 characters |
| An event's time | At most 5 minutes ahead of Audit's clock |
The Laravel SDK keeps to all of them: it sends 500 events at a time, halves a batch Audit finds too big, and throws for an event that is too big before it reaches the outbox.