Skip to content

Releases: jobec/rfc5424-logging-handler

1.4.3

19 May 14:25
Compare
Choose a tag to compare

Changed

  • #34 Allow enterprise ID to contain sub-identifiers.

Fixed

  • #31 Correct handling of failed connection attempt in TCP transport handler.

1.4.2

08 Apr 18:27
Compare
Choose a tag to compare

Changed

  • #32 address can now also be a list, making loading settings form a config file possible.

Added

  • Python 3.7 tests and support.

1.4.1

16 Feb 21:39
Compare
Choose a tag to compare

Fixed

  • #29 Fix AttributeError when using TLS connection.

1.4.0

30 Jan 20:31
Compare
Choose a tag to compare

Added

  • #27 Make it possible to log to streams as an alternate transport.
  • Added API documentation.

Changed

  • Syslog facilities and framing options have moved from the RfcSysLogHandler class
    to module level variables. You may have to adjust your references to them.

1.3.0

30 Jan 20:31
Compare
Choose a tag to compare

Added

  • #23 Add support for TLS/SSL

v1.2.1

21 Sep 18:26
Compare
Choose a tag to compare

Fixed

  • #21 Registered structured data IDs where also suffixed with an enterprise ID.

Added

  • #22 Add utc_timestamp parameter to allow logging in UTC time.

v1.1.2

03 Feb 19:13
Compare
Choose a tag to compare
  • #15 When logging to /dev/log with python 2.7, the connection was permanently lost when the local syslog server was restarted.
  • #16 The extra info of a message did not overwrite that of the logging adapter instance.

v1.0.2

31 Aug 09:38
Compare
Choose a tag to compare

Fixed package description rendering on PyPi due to bug pypa/wheel#189

v1.0.1

30 Aug 19:37
Compare
Choose a tag to compare

It's now possible to send syslog messages as MSG-ANY which suppresses the UTF-8 byte order mark (BOM) when sending messages.

v1.0.0

30 May 19:56
Compare
Choose a tag to compare

Procid, appname and hostname can now be set per message, both with the handler as well as with the adapter

note

This release has a slight change in behaviour. Setting one of the appnama, hostname of procid message to None of an empty string will cause it to be filled in automatically. Previously, setting it to an empty string caused it to be set to NILVALUE (a - ). You now need to set it explicilty to NILVALUE if you want to omit it from the message.