Insights & updates from our experts
A minor but helpful usability feature has been added for auditors and account administrators in the ‘Audit Entries’ section of the Settings console. In this section they have always been able to review audit entries. When they would select an entry, the entire audit trail that this entry is a part of opens on the right side of the screen.
If the record for which the selected audit entry was generated, had been updated several more times following the generation of the selected audit entry, the selected audit entry would be too far down the audit trail to be visible on the screen. In such cases, the auditor or administrator would have to scroll down until the selected audit entry, which would be highlighted in yellow, become visible.

This scrolling is no longer necessary because now the audit trail automatically scrolls down to the selected entry. The selected entry does not get presented at the very top of the screen, though. This ensures that the user is aware that the record was modified after the generation of the selected audit entry.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)

.webp)












