Initialize logging from a configuration json
Project description
sag_py_logging
This library can be used to initialize the python logging by loading a config json. Furthermore it provides a way to log extra fields.
What it does
- Initialize logging from configuration json
- Placeholder support for the config json
- A log filter to log extra fields
How to use
Installation
pip install sag-py-logging
pip install sag-py-logging[jinia] (optional for templating)
pip install sag-py-logging[toml] (optional for toml file support)
Initialize logging from json
Add the following as early as possible to your application code:
from sag_py_logging.log_config_initializer import init_logging
from sag_py_logging.log_config_loader import JsonLoader, TomlLoader
from sag_py_logging.log_config_processors import FormatProcessor, JinjaProcessor
placeholder_container = { "host": "myhost.com", ...}
# For toml config with jinja templating
init_logging(
"./log_config.toml",
loader=TomlLoader(),
processors=[JinjaProcessor(placeholder_container)]
)
# For json config with format templating
init_logging(
"./log_config.json",
loader=JsonLoader(),
processors=[FormatProcessor(placeholder_container)]
)
Init logging returns the log configuration as dictionary if needed for further processing.
The configuration
Json config:
{
"version": 1,
"disable_existing_loggers": false,
"root": {
"handlers": ["myhandler"],
"level": "INFO"
},
"handlers": {
"myhandler": {
"host": "${host}",
"formatter": "handler_formatter"
}
}
}
Toml config:
version = 1
disable_existing_loggers = false
[root]
handlers = ["myhandler"]
level = "INFO"
[handlers.myhandler]
host = "${host}"
formatter = "handler_formatter"
This is a very basic sample on the format of the file including placeholders.
Read the following for a full schema reference: https://docs.python.org/3/library/logging.config.html#configuration-dictionary-schema
Read more on string templating here: https://docs.python.org/3/library/string.html#template-strings
Or if you use jinja templating there: https://jinja.palletsprojects.com/en/3.1.x/templates/#template-designer-documentation
Configure extra field logging
It is possible to add a filter that extends log entries by a field for extra fields.
The filter is added like that if you initialize logging by code:
from sag_py_logging.console_extra_field_filter import ConsoleExtraFieldFilter
console_handler = logging.StreamHandler(sys.stdout)
console_handler.addFilter(ConsoleExtraFieldFilter())
If you init logging by config file the filter is added like that:
{
"formatters": {
"myformatter": {
"format": "s%(asctime)s - %(name)s - %(message)s - %(stringified_extra)s",
},
},
"filters": {
"console_extra_field_filter": {"()": "sag_py_logging.console_extra_field_filter.ConsoleExtraFieldFilter"}
},
"handlers": {
"myhandler": {
"formatter": "myformatter",
"filters": ["console_extra_field_filter"]
}
}
}
Afterwards you can use the field "stringified_extra" in your format string.
If you for example log the following:
logging.warning('Watch out!', extra={"keyOne": "valueOne", "keyTwo": 2})
The resulting log entry would look like that if stringified_extra is added to the end of the format string:
Watch out! {"keyOne": "valueOne", "keyTwo": 2}
Note: Internally json.dumps is used to convert the object/data to a string
How to start developing
With vscode
Just install vscode with dev containers extension. All required extensions and configurations are prepared automatically.
With pycharm
- Install latest pycharm
- Install pycharm plugin BlackConnect
- Install pycharm plugin Mypy
- Configure the python interpreter/venv
- pip install requirements-dev.txt
- pip install black[d]
- Ctl+Alt+S => Check Tools => BlackConnect => Trigger when saving changed files
- Ctl+Alt+S => Check Tools => BlackConnect => Trigger on code reformat
- Ctl+Alt+S => Click Tools => BlackConnect => "Load from pyproject.yaml" (ensure line length is 120)
- Ctl+Alt+S => Click Tools => BlackConnect => Configure path to the blackd.exe at the "local instance" config (e.g. C:\Python310\Scripts\blackd.exe)
- Ctl+Alt+S => Click Tools => Actions on save => Reformat code
- Restart pycharm
How to publish
- Update the version in setup.py and commit your change
- Create a tag with the same version number
- Let github do the rest
How to test
To avoid publishing to pypi unnecessarily you can do as follows
- Tag your branch however you like
- Use the chosen tag in the requirements.txt-file of the project you want to test this library in, eg.
sag_py_logging==<your tag>
- Rebuild/redeploy your project
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file sag_py_logging-0.4.0.tar.gz
.
File metadata
- Download URL: sag_py_logging-0.4.0.tar.gz
- Upload date:
- Size: 8.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.12.6
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 7d2ef4413022a7ddd2a743ec9ca7ca5afc7bfe1188cee5f4375a3728b791c060 |
|
MD5 | 03b3900bf0c05913f3dc521874f91274 |
|
BLAKE2b-256 | ec6bb05dfbfe7616f48b2a2ce06820a2554c3734093e08e27d9e43e2da7c28d8 |
File details
Details for the file sag_py_logging-0.4.0-py3-none-any.whl
.
File metadata
- Download URL: sag_py_logging-0.4.0-py3-none-any.whl
- Upload date:
- Size: 7.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.12.6
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 9deb13bebcfdff51acae98b1b742c60558ff1b432773fa37d2e098a240eda4c1 |
|
MD5 | 44747e5af4204e2d17e3f597af186bd8 |
|
BLAKE2b-256 | 4cc4de18a7a396589e5aa42d8595975d98b965fd2ffcf8de24a1bb3d7769ff41 |