# Record and timestamp problem in audit.log

**URL:** <https://forums.percona.com/t/record-and-timestamp-problem-in-audit-log/14989>\
**Category:** Percona Server for MySQL 8.0\
**Created:** [March 30, 2022, 12:24pm UTC](https://forums.percona.com/t/record-and-timestamp-problem-in-audit-log/14989 "2022-03-30T12:24:16Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [April 2, 2022, 3:46am UTC](https://forums.percona.com/t/record-and-timestamp-problem-in-audit-log/14989/5 "2022-04-02T03:46:25Z")

</div>

According to the bug you provided, it is not an issue/bug. Timestamp information in the audit log is always logged in UTC. The manual states this. The bug you linked is a feature request to have the audit timestamp be timezone sensitive. For now, the solution seems to have your qradar parse the timestamp in UTC and convert it on import.

---

_[View the full topic](https://forums.percona.com/t/record-and-timestamp-problem-in-audit-log/14989)._