VYPR
trendPublished Nov 22, 2026· 1 source

Debian and Ubuntu Shift Syslog Timestamps to ISO-8601, Impacting Centralized Logging

Recent Debian and Ubuntu releases have changed the default syslog timestamp format from the traditional BSD style to ISO-8601, affecting administrators managing centralized logging systems.

Administrators managing centralized logging infrastructure have likely noticed a change in the timestamp format of syslog messages originating from newer Debian and Ubuntu systems. Historically, syslog messages used the familiar "Mmm dd hh:mm:ss" format, a standard dating back to the early days of Unix debugging. However, recent releases, specifically Debian 12 (Bookworm) and Ubuntu 23.04, have shifted this default to the more modern ISO-8601 (RFC 3339) format.

This change is primarily driven by the increased adoption of systemd-journald as the default logging mechanism in these distributions. Consequently, the rsyslogd package, which many administrators still rely on for forwarding logs to central servers or Security Information and Event Management (SIEM) systems, no longer defaults to the traditional format. The RSYSLOG_TraditionalFileFormat directive, which controlled this behavior, has been removed from the default rsyslogd configuration files in these newer versions.

The syslog protocol itself has a long history, originating in 1983 with Eric Allman's work on sendmail debugging. It was incorporated into BSD 4.2 that same year and later integrated into AT&T's System V Unix. The first formal standardization effort led to RFC 3164 in 2001, defining the widely recognized "BSD syslog" format. While rsyslogd itself added support for RFC 3339 timestamps around 2005, and RFC 5424 superseded RFC 3164 in 2009 with its own timestamp specifications, most Linux distributions continued to use the older BSD format by default.

For system administrators who have established workflows and parsing rules based on the traditional BSD timestamp format, this shift can cause immediate disruption. These administrators often continue to install rsyslogd even when systemd-journald is present, due to existing infrastructure for log aggregation and analysis. The change in timestamp format can break log correlation, SIEM ingestion, and automated log parsing scripts, requiring updates to accommodate the new ISO-8601 standard.

While Debian and Ubuntu have made this change, other major Linux distributions have maintained the traditional format as the default for rsyslogd. Fedora and AlmaLinux, for instance, continue to include the RSYSLOG_TraditionalFileFormat directive in their default configurations, offering a smoother transition for administrators migrating to or managing systems across different distributions.

For those needing to revert to the traditional format or explicitly configure ISO-8601 timestamps, journalctl offers options to control output. Setting the output format to short yields the BSD format, while short-iso-precise provides the ISO format. Additionally, alternative syslog daemons like syslog-ng also support ISO timestamp formatting, which can be enabled via configuration options such as ts-format(iso) and frac-digits(6).

This change highlights the ongoing evolution of logging standards and the challenges faced by system administrators in maintaining consistency across diverse environments. As distributions move towards more modern, standardized formats like ISO-8601, it underscores the importance of staying informed about default configuration changes and adapting logging strategies accordingly to ensure effective security monitoring and incident response.

Synthesized by Vypr AI