20 breaking releases

0.21.0 Nov 13, 2023
0.19.0 Jul 30, 2023
0.18.0 Sep 30, 2022
0.17.0 Jun 17, 2022
0.2.0 Feb 9, 2020

#173 in Parser implementations

Download history 2976/week @ 2023-08-02 2514/week @ 2023-08-09 2862/week @ 2023-08-16 4434/week @ 2023-08-23 3512/week @ 2023-08-30 3655/week @ 2023-09-06 4419/week @ 2023-09-13 3351/week @ 2023-09-20 4458/week @ 2023-09-27 4287/week @ 2023-10-04 3458/week @ 2023-10-11 3654/week @ 2023-10-18 5189/week @ 2023-10-25 3927/week @ 2023-11-01 3819/week @ 2023-11-08 3242/week @ 2023-11-15

16,795 downloads per month
Used in 2 crates

MIT license

1.5K SLoC

Syslog Loose

A simple parser that aims to parse syslog messages. The goal is to extract as much correct information from the message rather than to be pedantically correct to the standard.

There are two standards for formatting Syslog messages.


RFC5424 is well defined and unambiguous. Syslog-loose fill first attempt to parse the message according to this standard. Many systems do not produce messages according to RFC5424 unfortunately, so if this fails it will fall back to:


RFC3164 is a much looser, more ambiguous format.

Lets look at a sample message:

<34>Oct 11 22:14:15 mymachine su: 'su root' failed for lonvick on /dev/pts/8

The first field <34> is a combination of the facility and severity of the message. This can be missing, if so None is returned for both fields. See here.

The date field, technically for 3164 it needs to be in the format MMM DD HH:MM:SS. There is no year specified. It is possible to pass a function to parse_message_with_year that you can use to resolve the year. For example, you may want to resolve all dates to the current year unless it is the 1st January and you have a log message from the 31st December.

The parser will also work for timestamps in 3339 format (eg. 1985-04-12T23:20:50.52Z).

The next two fields are optional and are the hostname or the appname together with the (optional) process id. These fields should be terminated by a :. For example:

mymachine app[323] :

This gives us:

hostname = mymachine appname = app procid = 323

mymachine app :

hostname = mymachine appname = app procid = None

mymachine :

hostname = mymachine appname = None procid = None

app[323] :

This gives us:

hostname = None appname = app procid = 323

The text following the : is the message. The message can first start with structured data, comprising one or more sections surrounded by [ and ] in the format: [id key="value"..]. Multiple key value pairs, separated by space, can be specified. Any remaining text is parsed as the free-form message. Any structured data sections that fail to parse are ignored.


fn resolve_year((month, _date, _hour, _min, _sec): syslog_loose::IncompleteDate) -> i32 {
    let now = Utc::now();
    if now.month() == 1 && month == 12 {
        now.year() - 1
    } else {

parse_message_with_year(msg, resolve_year, Variant::Either)


Dates in a RFC3164 message may not necessarily specify a Timezone. If you wish to specify a timezone manually you can parse the message with parse_message_with_year_tz. The tz parameter contains an Option of a chrono FixedOffset that specifies the offset from UTC.

If no timezone is specified the date will be parsed in the local time - unless that time cannot exist in the local timezone (that nonexistent period of time when clocks go forward), then the timezone will be parsed as UTC.


~41K SLoC