rfc5424-logging-handler

v1.4.3

An up-to-date, RFC5424-Compliant syslog handler for the Python logging framework For more information about how to use this package see README

Latest version published 6 years ago

License: BSD-3-Clause

PyPI

GitHub

Package Health Score

49 / 100

security
No known security issues
popularity
Recognized
maintenance
Inactive
community
Limited

Popularity

Recognized

GitHub Stars: 49
Forks: 23
Contributors: 8

Direct Usage Popularity

Based on project statistics from the GitHub repository for the PyPI package rfc5424-logging-handler, we found that it has been starred 49 times.

Security

No known security issues

Security and license risk for latest version

Release Date: May 19, 2019
Direct Vulnerabilities: 0
C
0
H
0
M
0
L
Indirect Vulnerabilities: 0
C
0
H
0
M
0
L
License Risk: 0
H
0
M
0
L

All security vulnerabilities belong to production dependencies of direct and indirect packages.

License

BSD-3-Clause

Security Policy

We found a way for you to contribute to the project! Looks like rfc5424-logging-handler is missing a security policy.

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 8
Open PR: 5
Last Release: 6 years ago
Last Commit: 5 years ago

Further analysis of the maintenance status of rfc5424-logging-handler based on released PyPI versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for rfc5424-logging-handler is that it hasn't seen any new versions released to PyPI in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Community

Limited

Readme: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 8
Funding: Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like rfc5424-logging-handler is missing a Code of Conduct.

Embed Package Health Score Badge

Keep your project healthy

Check your requirements.txt

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Python Versions Compatibility: ==2.7.*, ==3.4.*, ==3.5.*, ==3.6.*, ==3.7.*

Age: 8 years
Latest Release: 6 years ago
Dependencies: 2 Direct / 3 Total
Versions: 17
Maintainers: 1
Wheels: OS Independent

Readme

Python rfc5424 syslog logging handler

An up-to-date, RFC 5424 compliant syslog handler for the Python logging framework.

Free software: BSD License
Homepage:
Documentation:

Features

RFC 5424 Compliant.
Python Logging adapter for easier sending of rfc5424 specific fields.
No need for complicated formatting strings.
TLS/SSL syslog support.
Alternate transports like streams (ex. stderr, stdout, file, ...).

Installation

Python package:

pip install rfc5424-logging-handler

Usage

After installing you can use this package like this:

import logging
from rfc5424logging import Rfc5424SysLogHandler

logger = logging.getLogger('syslogtest')
logger.setLevel(logging.INFO)

sh = Rfc5424SysLogHandler(address=('10.0.0.1', 514))
logger.addHandler(sh)

logger.info('This is an interesting message', extra={'msgid': 'some_unique_msgid'})

This will send the following message to the syslog server:

&lt;14&gt;1 2020-01-01T05:10:20.841485+01:00 myserver syslogtest 5252 some_unique_msgid - \xef\xbb\xbfThis is an interesting message

Note the UTF8 Byte order mark (BOM) preceding the message. While required by RFC 5424 section 6.4 if the message is known to be UTF-8 encoded, there are still syslog receivers that cannot handle it. To bypass this limitation, when initializing the handler Class, set the msg_as_utf8 parameter to False like this:

sh = Rfc5424SysLogHandler(address=('10.0.0.1', 514), msg_as_utf8=False)

For more examples, have a look at the documentation

Changelog

1.4.3 - 2019/05/19

Changed

#34 Allow enterprise ID to contain sub-identifiers.

Fixed

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

1.4.2 - 2019/04/08

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 - 2019/02/16

Fixed

#29 Fix AttributeError when using TLS connection.

1.4.0 - 2019/01/30

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 - 2018/10/19

Added

#23 Add support for TLS/SSL

1.2.1 - 2018/09/21

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.

1.1.2 - 2018/02/03

Fixed

#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.

1.1.1 - 2017/12/08

Fixed

#14 Fixed handling of extra parameter in logging adapter.

1.1.0 - 2017/11/24

Added

The msg parameter for the logger handler can now be absent allowing "structured data only" messages.

Fixed

Correct the automatic value of the hostname when the value is anything other then NILVALUE
The syslog message is now empty in conformance with RFC5424 when it's value is None or an empty string.

1.0.3 - 2017/10/08

No functional changes. Only documentation was changed.

Added

Logstash configuration example for RFC5424.

Changed

Moved most of the documentation out of the readme file.

1.0.2 - 2017/08/31

Fixed

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

1.0.1 - 2017/08/30

Added

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

1.0.0 - 2017/05/30

Changed

#10: 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 or 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.

0.2.0 - 2017/01/27

Fixed

Better input handling
Better sanitizing of invalid input

0.1.0 - 2017/01/22

Added

#4: Adapter class to make it easier to log message IDs or structured data
Logging of EMERGENCY, ALERT and NOTICE syslog levels by using the adapter class
Extensive test suite

0.0.2 - 2017/01/18

Added

#5 Introduced Python 2.7 compatibility

0.0.1 - 2017/01/11

Initial release

rfc5424-logging-handler dependencies

pytz tzlocal

FAQs

What is rfc5424-logging-handler?

An up-to-date, RFC5424-Compliant syslog handler for the Python logging framework. Visit Snyk Advisor to see a full health score report for rfc5424-logging-handler, including popularity, security, maintenance & community analysis.

Is rfc5424-logging-handler popular?

The python package rfc5424-logging-handler receives a total of 11,981 weekly downloads. As such, rfc5424-logging-handler popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is rfc5424-logging-handler well maintained?

We found indications that rfc5424-logging-handler is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is rfc5424-logging-handler safe to use?

The python package rfc5424-logging-handler was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 19 November-2024, at 10:10 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Direct Usage Popularity

Security and license risk for latest version

Commit Frequency

Embed Package Health Score Badge

Keep your project healthy

Check your requirements.txt

Snyk Vulnerability Scanner

Readme

Python rfc5424 syslog logging handler

Features

Installation

Usage

Changelog

1.4.3 - 2019/05/19

1.4.2 - 2019/04/08

1.4.1 - 2019/02/16

1.4.0 - 2019/01/30

1.3.0 - 2018/10/19

1.2.1 - 2018/09/21

1.1.2 - 2018/02/03

1.1.1 - 2017/12/08

1.1.0 - 2017/11/24

1.0.3 - 2017/10/08

1.0.2 - 2017/08/31

1.0.1 - 2017/08/30

1.0.0 - 2017/05/30

0.2.0 - 2017/01/27

0.1.0 - 2017/01/22

0.0.2 - 2017/01/18

0.0.1 - 2017/01/11

rfc5424-logging-handler dependencies

FAQs

What is rfc5424-logging-handler?

Is rfc5424-logging-handler popular?

Is rfc5424-logging-handler well maintained?

Is rfc5424-logging-handler safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues