logzio-python-handler
Logging handler to send logs to your Logz.io account with bulk SSL
Decision gist · record as of 2026-08-14
Yes. This is a stable, actively maintained handler with low install friction, no known vulnerabilities, and permissive licensing. Install it if you use Logz.io and want to ship Python application logs via the standard logging module with built-in retry and fallback behavior. The only caveat is to verify that protobuf is actually needed for your use case, as it appears to be a transitive dependency rather than a direct requirement.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires a valid Logz.io account token and network access to the Logz.io listener endpoint (defaults to https://listener.logz.io:8071).
- Low install friction with only two runtime dependencies (requests and protobuf).
- Actively maintained with recent commits and tested against modern Python versions from 3.5 through 3.14.
License · maintenance · safety
Apache License 2 (permissive) — Licensed under Apache License 2 (permissive), allowing use in most commercial and open-source projects without significant restrictions.
last release 2026-02-01 (194 days) · last repo commit 2026-07-27 · 36 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 950,948 downloads/mo, #4,658 on PyPI
Alternatives
Verify before relying
import logging
import logging.config
LOGGING = {
'version': 1,
'handlers': {
'logzio': {
'class': 'logzio.handler.LogzioHandler',
'token': 'YOUR_LOGZIO_TOKEN',
'logzio_type': 'python-handler',
'url': 'https://listener.logz.io:8071',
}
},
'root': {'handlers': ['logzio'], 'level': 'INFO'}
}
logging.config.dictConfig(LOGGING)
logger = logging.getLogger()
logger.info('Test log')- Whether protobuf is actually used at runtime or is a transitive dependency that could be removed
- Performance characteristics when handling high-volume log streams or large individual log entries
- Behavior and data retention of local filesystem fallback when Logz.io is unreachable
What it is and what it does
This package provides a Python logging handler that integrates with Python's standard logging module to ship logs to Logz.io. It queues logs in a background thread, batches them by size, and sends them over HTTPS in bulk. If the main thread exits, it drains the queue one final time before shutting down. When logs fail to send after retries, they are written to the local filesystem as a fallback, allowing manual recovery later via curl.
The handler is designed for applications that need centralized log aggregation without blocking on network I/O. It supports configuration via Python's logging config file format or dict config, dynamic extra fields per log entry, and optional trace context correlation when using OpenTelemetry instrumentation. The package has been in production use since 2016 and is actively maintained.
Use it for
- Centralize application logs from multiple Python services into a single Logz.io account for unified monitoring and search.
- Batch log shipment in background threads to avoid blocking application code on network latency or Logz.io availability.
- Automatically retry failed log sends and persist logs locally when Logz.io is temporarily unreachable.
- Add dynamic metadata fields to individual log entries without pre-configuring them in the handler setup.
- Correlate application logs with distributed traces by enabling OpenTelemetry trace context enrichment.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
This is a stable, actively maintained handler with low install friction, no known vulnerabilities, and permissive licensing. Install it if you use Logz.io and want to ship Python application logs via the standard logging module with built-in retry and fallback behavior. The only caveat is to verify that protobuf is actually needed for your use case, as it appears to be a transitive dependency rather than a direct requirement.
Install
logzio-python-handler on PyPI
Before you install
Low install friction with only two runtime dependencies (requests and protobuf). Actively maintained with recent commits and tested against modern Python versions from 3.5 through 3.14.
Requires a valid Logz.io account token and network access to the Logz.io listener endpoint (defaults to https://listener.logz.io:8071).
License in practice
Licensed under Apache License 2 (permissive), allowing use in most commercial and open-source projects without significant restrictions.
Quickstart
import logging
import logging.config
LOGGING = {
'version': 1,
'handlers': {
'logzio': {
'class': 'logzio.handler.LogzioHandler',
'token': 'YOUR_LOGZIO_TOKEN',
'logzio_type': 'python-handler',
'url': 'https://listener.logz.io:8071',
}
},
'root': {'handlers': ['logzio'], 'level': 'INFO'}
}
logging.config.dictConfig(LOGGING)
logger = logging.getLogger()
logger.info('Test log')Verify before relying
- Whether protobuf is actually used at runtime or is a transitive dependency that could be removed
- Performance characteristics when handling high-volume log streams or large individual log entries
- Behavior and data retention of local filesystem fallback when Logz.io is unreachable
Package facts
| License | Apache License 2 permissive |
| Python support | Not specified |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagesrequestsprotobuf |
| Maintenance | Actively maintained 194 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 950,948 / month, #4,658 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableIntended Audience :: DevelopersProgramming Language :: Python :: 3.9 |
Evidence: logzio_python_handler-4.1.9-py2.py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “logz.io logging handler”
- logzio-python-handlerA Python logging handler that sends logs in bulk over HTTPS to…
- loki-logger-handlerA logging handler that sends Python log messages to Grafana Loki in…
- cloudwatchA Python logging handler that sends log events to AWS CloudWatch,…
Give your agent the search over MCP, or paste the wish link into any chat.
More Monitoring packages
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
Provides generated Python code for OpenTelemetry semantic conventions, enabling standardized attribute naming and constant definitions for instrumentation and telemetry collection.
Install it if you are using OpenTelemetry and want to follow semantic conventions correctly.
Provides the reference implementation of the OpenTelemetry API for collecting and exporting traces, metrics, and logs from Python applications.
Provides the abstract API and interfaces for OpenTelemetry instrumentation in Python, defining how to emit traces, metrics, and logs without tying code to a specific SDK implementation.
Exports OpenTelemetry observability data to an OpenTelemetry Collector using Protobuf-encoded messages over HTTP.
Install it if you are using OpenTelemetry in Python and need to send data to a Collector over HTTP.
Provides automatic instrumentation commands and programmatic APIs to inject distributed tracing into Python applications without code changes, detecting and instrumenting packages used by your program.
Install it if you need distributed tracing without code changes and have compatible instrumented packages in your environment.
See also splunk-handler · logging-azure-rest · pygelf · python3-logstash · python-logging-loki · cloudwatch · fluent-logger · libadvian · watchtower · graypy