🔒Audit Logs, Rebuilt From the Ground Up
The Audit Logs module has been completely redesigned — and the difference is significant. What used to be a single, flat table trying to answer two very different questions at once has been split into two dedicated tabs: Events, for tracking what happened to your entities (who created, updated, or deleted a device, dashboard, incident, and so on), and Requests, for the raw HTTP calls behind those changes. On top of that, the scope of what gets tracked has expanded, covering a broader set of platform entities than before.
But the biggest improvement isn't just what gets logged — it's how easy it now is to make sense of it. Instead of digging through raw JSON blobs and header dumps, each event now shows you a clean before/after diff that answers the question you actually care about: what specifically changed, when, and who did it. The Requests tab surfaces the same kind of clarity for HTTP-level detail, with all the relevant fields front and center. Whether you're auditing a configuration change, investigating an unexpected action, or just keeping tabs on your account's activity, the new Audit Logs gives you the full picture without the friction.
Note: Because this redesign involved changes to the underlying engine, historical logs from the previous version are not carried over automatically. If you need your prior records, reach out to [email protected] and we'll export them for you.