Who is this article for?

Users, administrators and support engineers wanting to know more about timestamp formats.

No special permissions are required.

Ideagen Internal Audit Aura V6 uses different timestamp formats across its various components, with some logging in UTC and others using the server's regional time.

Service/TngService.svc timestamps

The Service/TngService.svc component logs initial startup in UTC. Events are timestamped with UTC values, except for the initialisation event, which is reported in the server's regional time but incorrectly marked as Z (UTC indicator).

Example:

On a server based in the US eastern region during daylight savings time:

2027-09-18 07:59:18.381 TngService initialization completed at: 2027-09-18 03:59:18Z

In this example, the service starts at 07:59 UTC and reports completion at 03:59. Although marked 'Z', this is actually 03:59 EDT (the server's clock time), not UTC.

WebService/TngWebService.svc timestamps

The Web service logs all events in UTC.

Pentana Robot timestamps

Initial startup is logged in UTC, but some jobs log at the server's current local time.

Note: For more details about Robot activity logging inconsistencies, see Inconsistencies in Robot activity logging.

IIS timestamps

IIS logs all events in UTC.

Database timestamps

In the database, log entries in the *_log.ByTime columns use UTC.

Client log file timestamps

Client log files located at %localappdata% use UTC.