Bug ID 998649: Hostnames that contain a period are logged incorrectly

Last Modified: Apr 11, 2024

Affected Product(s):
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,,,,,,, 14.1.5, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3

Fixed In:

Opened: Mar 02, 2021

Severity: 2-Critical


Sylog-ng uses the hostname (machine name) and truncates it starting at the first '.' (period). This results in hostnames that contain a period being logged incorrectly (for example, 'my.hostname' is logged as 'my' by syslog-ng). Additionally, hostnames are being truncated in bootmarker logs and the ltm, apm, apm, ipsec, saas, and fw_log that are sourced from TMM. Three sub-bugs BZ1076909, BZ1076921, BZ1080317 are created and BZ998649 is the base bug for tracking the above three issues.


Some logs that go directly to syslog-ng use a truncated hostname. Logs sourced from TMM uses truncated hostname.


Hostname contains a period '.' (For example 'my.hostname').



Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips