If we dive the source code,
% rpm -qi audit | grep http
Packager : CentOS BuildSystem <http://bugs.centos.org>
URL : http://people.redhat.com/sgrubb/audit/
...
% git clone https://github.com/linux-audit/audit-userspace.git
% cd audit-userspace/
And then make a guess that the epoch is a %d
flag to printf
followed by a colon (it might also be a %ld
or %u
or %lu
depending on whether long
or unsigned
is for some reason involved):
% grep -ri '%d:' . | tail -1
./auparse/test/auparse_test.py: print(" event time: %d.%d:%d, host=%s" % (event.sec, event.milli, event.serial, none_to_null(event.host)))
we find some test code that indicates the fields are second, millisecond, and some sort of event serial number. From additional digging it appears these values are grouped together as they all belong to a particular memory structure. Hopefully the docs will have more information about what that serial number is...
.760
is likely to be milliseconds.:2358773
is likely not to be part of the timestamp. Without information as to what generates that audit log, it's hard to tell what it might be.