Bug ID 998649: Log hostname should be consistent when it contains ' . '

Last Modified: Apr 25, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,

Opened: Mar 02, 2021
Severity: 2-Critical


Messages that are logged to journald use the configured hostname, while sylog-ng uses the hostname (machine name) and truncates it starting at the first '.' (period). This results in hostnames being inconsistent when it contains '.'; e.g., 'my.hostname' is logged as 'my' by syslog-ng, and 'my.hostname' by journald. This can make it difficult for log analysis tools to work with the log files.


The full hostname is logged for system logs while logs that go directly to syslog-ng use a truncated hostname.


-- Hostname contains a period -- Viewing log files emitted from journald and from syslog-ng



Fix Information


Behavior Change