This release is a pre-release and may not be stable for production use.
The goal is to provide distributed logging aggregation points, initially for syslog with longer term plans for other on-box logs. Aggregation points can be implemented close to the logging source either on a network device or other 3rd party compute node. Logging can be segmented into clusters with a hierarchy in each cluster. Message back-up/availability is built into the cluster logging architecture. Message dedup is the function of the ‘search head’. Each cluster has its own northbound API front end as part of a search head to be integrated with other systems.
1 maintainer
Metadata
1 maintainer
Release files for logBlizzard 0.5.dev9
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 | Reset |
|---|---|---|---|---|
| logBlizzard-0.5.dev9-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Release files / logBlizzard-0.5.dev9-py2.py3-none-any.whl
| Download URL | logBlizzard-0.5.dev9-py2.py3-none-any.whl |
|---|---|
| Size | 18.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7c57a60e810548688455201333d5c424d32e18c16b075bd05c7c1be3a767bc36
|
|
BLAKE2b-256 checksum How to use checksums |
5952aefa9cdf9f903fd5b4173dcd32135b4934552e865f2ada40c73d3e974f3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for logBlizzard 0.5.dev9
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.
