logger-py | Bunyan like logger for python

by Sagacify Python Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | logger-py Summary

logger-py is a Python library typically used in Logging applications. logger-py has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

Bunyan like logger for python

Support

Quality

Security

License

Reuse

Support

logger-py has a low active ecosystem.

It has 4 star(s) with 1 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

logger-py has no issues reported. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of logger-py is current.

Quality

logger-py has no bugs reported.

Security

logger-py has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

logger-py is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

logger-py releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed logger-py and discovered the below as its top functions. This is intended to give you an instant insight into logger-py implemented functionality, and help decide if they suit your requirements.

Format a log record
Return a formatted time string
Return the app name and version
Extract the name from the command line arguments
Extra serializer
Serialize an error

Get all kandi verified functions for this library.

logger-py Key Features

No Key Features are available at this moment for logger-py.

logger-py Examples and Code Snippets

No Code Snippets are available at this moment for logger-py.

Community Discussions

Trending Discussions on logger-py

How to log a error to Stackdriver Error Reporting via Stackdriver Logging in Python

logger.disabled check much later in python logging module. What's the rationale?

QUESTION

How to log a error to Stackdriver Error Reporting via Stackdriver Logging in Python

Asked 2019-Nov-15 at 18:26

I've been using Stackdriver Logging for a long time and now I'd like to also take advantage of Error Reporting. I'd prefer to use Python's logging mechanism and scrape exceptions out of a log file if possible (for various reasons) rather than using the error_reporting library. That being said, the documentation is very confusing. For example the documentation says: https://cloud.google.com/error-reporting/docs/setup/compute-engine#log_exceptions

First, install the fluent-logger-python library:

sudo pip install google-cloud-error-reporting --upgrade

which leads me to believe that google-cloud-error-reporting is a fork of or related to fluent-logger-python however, when I initialize google-cloud-error-reporting it directly calls out to the GCE metadata server rather than connecting to the local fluentd. Are these two unrelated packages or is the documentation wrong or misleading? If I send JSON formatted exceptions to fluentd or to a log file monitored by fluentd will error reporting understand them?

Thanks for any clarifications

...

ANSWER

Answered 2017-Sep-06 at 22:20

The documentation is wrong.
TL;DR You have to output something that looks like https://cloud.google.com/error-reporting/docs/formatting-error-messages

Here's my solution:

Source https://stackoverflow.com/questions/46009149

QUESTION

logger.disabled check much later in python logging module. What's the rationale?

Asked 2018-Jun-02 at 01:52

I am going through the code of python logging module both in Python2(2.7.12 default on Ubuntu 16.04) and Pyton 3.5 (3.5.2 default on Ubuntu 16.04).

The question is - if we look at the implementation of def _log that eventually calls self.handle, the check about self.disabled is done actually made in the handle method, but it's not done in the _log method.

Agree, checking it again in self.handle might make sense, but why not check it first thing in self._log or even better in self.isEnabledFor that avoids doing a lot of work that is done in self._log method.

What is it that I am missing?

Update: Did some profiling when logger is disabled - The code is in the following gist.

Following gists have the actual cprofile data indicating performance impact when the logger is disabled and when the logger is enabled.

It appears, there's considerable performance impact when the logger is disabled.

May be it is worth considering?

...

ANSWER

Answered 2018-Jun-02 at 01:52

This indeed was an issue and is fixed now -

https://github.com/python/cpython/commit/6e3ca645e71dd021fead5a70dc06d9b663612e3a

Source https://stackoverflow.com/questions/50453121

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install logger-py

You can download it from GitHub.
You can use logger-py like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: