Skip to content

RFC3164 must include the timestamp Nov 12 22:35:48 #5430

@thalesmaoa

Description

@thalesmaoa

Am I missing something, or is the timestamp missing in L137?

// An RFC3164 compliant message must be formated like : "<PRIO>[TimeStamp ]Hostname TaskName: Message"
// Using Settings.Name as the Hostname (Hostname must NOT content space)
{
String header;
header += '<';
header += prio;
header += '>';
header += NetworkCreateRFCCompliantHostname(true);
header += F(" EspEasy: ");
header.trim();
header.replace(' ', '_');

I had no problem with syslog until I realised that I needed the standardised format.

ts=2025-11-12T22:52:01.321316056Z level=warn msg="error parsing syslog stream" component_path=/ component_id=loki.source.syslog.local err="expecting a Stamp timestamp [col 3]"
ts=2025-11-12T22:52:07.360512543Z level=warn msg="error parsing syslog stream" component_path=/ component_id=loki.source.syslog.local err="expecting a Stamp timestamp [col 3]"
ts=2025-11-12T22:52:12.721814062Z level=warn msg="error parsing syslog stream" component_path=/ component_id=loki.source.syslog.local err="expecting a Stamp timestamp [col 3]"
ts=2025-11-12T22:52:17.360585911Z level=warn msg="error parsing syslog stream" component_path=/ component_id=loki.source.syslog.local err="expecting a Stamp timestamp [col 3]"
ts=2025-11-12T22:52:17.367005791Z level=warn msg="error parsing syslog stream" component_path=/ component_id=loki.source.syslog.local err="expecting a Stamp timestamp [col 3]"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions