exasupport now generates human-readable timestamps in content.txt
Details
| Detail name | Value |
|---|---|
| Changelog Number | 20745 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.25.0 |
| Fix Versions | Exasol 8.29.0 |
| Resolution Date | 2024-07-12 |
Description
Ever since the last major refactoring, exasupport log collection tool printed start/stop times in file content.txt in seconds since the Unix epoch. For instance:
Start date: 1716200000 Stop date: 1716300000
Workaround
Any programmatic way of converting Unix timestamps to text form could be used to know which settings were used to generate the logs. For example for python:
>>> from datetime import datetime, timezone
>>> ts = 1716200000
>>> print(datetime.fromtimestamp(ts, timezone.utc).strftime('%Y-%m-%d %H:%M:%S'))
2024-05-20 10:13:20
Fix
This has now been changed to make it more palatable to human consumers, who might want to verify manually that the time period for which logs were collected is correct. The new behavior looks like this (the user’s local time zone will be used):
Start date: 2024-05-20 10:13:20 GMT +0000 Stop date: 2024-05-21 14:00:00 GMT +0000
Functionality is not affected (except for the unlikely case that someone has written an automated parser for these timestamps, which would have to be adjusted to use e.g. a "%Y-%m-%d %H:%M:%S %Z %z" format string for Python’s time.strptime()).
