eiq_logging
This package exists to make it easy to configure logging in a consistent way across multiple EclecticIQ Python projects.
Installation
pip install eiq-logging
Usage
In your application's entrypoint, whatever that may be:
import eiq_logging
eiq_logging.configure()
The configure function takes a few arguments:
streamdetermines where logs are written. Defaults tosys.stderr.log_formatcan be either "plain" or "json". "plain" means plain text and is meant to be read by humans. "json" is newline-delimited JSON, meant for log aggregation and machine parsing.log_levelscan be either a dict of{logger_name: log_level}or a string which will be parsed as such. The string is comma-separated, and each item in the string should be in the format of "logger_name:log_level" - for example,root:info,example:debugwill set the root logger to the level INFO, and the logger "example" to level DEBUG.
If you leave out the log_format and log_level arguments, you can configure these through the environment variables EIQ_LOG_FORMAT and EIQ_LOG_LEVEL.
If you're using Gunicorn, you don't need to call configure yourself, you can just start the process with the --config flag:
gunicorn --config=python:eiq_logging.gunicorn myapp
Metadata
Release files for eiq-logging 1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| eiq-logging-1.4.tar.gz | 5.5 kB | Without provenance | Details for eiq-logging-1.4.tar.gz |
Release files / eiq-logging-1.4.tar.gz
| Download URL | eiq-logging-1.4.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b83f43f137dc872fa49ce1c0ffcea9b9625bfb32cc13f3b0d162c0bd63dcc49
|
|
BLAKE2b-256 checksum How to use checksums |
b4e4a4a2d469fd864b26b53b0b90228b0c6b1079ea7aa5994fa8228b6684ac8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.7.3
|
Security for eiq-logging 1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.