Releases: jobec/rfc5424-logging-handler
Releases · jobec/rfc5424-logging-handler
1.4.3
Changed
- #34 Allow enterprise ID to contain sub-identifiers.
Fixed
- #31 Correct handling of failed connection attempt in TCP transport handler.
1.4.2
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
Fixed
- #29 Fix AttributeError when using TLS connection.
1.4.0
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
Added
- #23 Add support for TLS/SSL
v1.2.1
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
- #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.1
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
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.