log-proxy
This package implements a logging server which can be secured with TLS. The server can forward the logs to another server allowing the definition of gateways. The transmission happens using JSON instead of pickle used by pythons SocketHandler to prevent code execution.
The main purpose of this project is to aggregate logs via the network inside of a database like PostgreSQL or MongoDB. The client is able to collect the logs from different sources.
This tool is not designed to later process, view, or manage the logs inside of the database.
Features
- Log aggregation and proxy servers
- Forward the logs in a server to another server or database (MongoDB, PostgreSQL)
- Logging handlers to send logs to the logging server from existing apps
- Client tool for testing
- Secure the transmission with TLS and token authentication
Usage examples
Start a logging server and forward the logs to a MongoDB database
$ python3 -m log_proxy server mongodb --db logs --db-table log <...>
Start a logging server and forward the logs to the next server
$ python3 -m log_proxy server socket --forward <host>
Start client for testing
$ python3 -m log_proxy client --forward <host> --log-stdin
Metadata
Release files for log-proxy 2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| log_proxy-2.0-py3-none-any.whl | Python 3 | none | any | Details for log_proxy-2.0-py3-none-any.whl |
Release files / log_proxy-2.0-py3-none-any.whl
| Download URL | log_proxy-2.0-py3-none-any.whl |
|---|---|
| Size | 15.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8a81b98717b1530e66c00859967a5a0e553c291776d84aeedc7925153d82a8d
|
|
BLAKE2b-256 checksum How to use checksums |
4a4a0b3eb3dddb9e83f14d63f9673d989cb44a2b59d71b6a023e42cb65d457bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for log-proxy 2.0
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.