GitHub Actions and GitLab CI runners use zxdl to stream build logs in real‑time to a central ELK stack. The JWT rotation feature allows short‑lived tokens scoped per pipeline run.
Tests conducted on a c5.large AWS instance (2 vCPU, 4 GB RAM) with a remote collector in the same region:
| Metric | v1.4.2 | v2.0.0 | Improvement | | --------------------------- | ------------- | -------------- | ----------- | | Max sustainable EPS | 3,200 | 8,900 | +178% | | P99 latency per batch (100 events) | 212 ms | 87 ms | -59% | | Memory footprint (idle) | 11 MB | 18 MB | +64% (trade‑off for buffer) | | CPU usage at 5k EPS | 0.8 cores | 0.6 cores | -25% |
Note: Memory increase is due to the new pre‑allocated ring buffer. You can set ZXDL_BUFFER_MB=4 to reduce.
Users can now specify shell commands to run after downloads complete—automatically unpacking archives, moving files to Plex directories, or executing antivirus scans. zxdl script github updated
The updated ZXDL script introduces a more intuitive configuration file: zxdl.config.ini. Below is a sample configuration leveraging the new features:
[General] output_directory = ~/Downloads/zxdl_output max_connections = 64 timeout_seconds = 30[Advanced] enable_chunk_hashing = true retry_attempts = 5 proxy_type = socks5 proxy_address = 127.0.0.1:9050
[PostProcess] hook_enabled = true hook_command = "unzip -o filepath -d output_dir && rm filepath"
To use the updated cookie function:
./zxdl.py --cookie-from-browser chrome https://example.com/video.m3u8
The zxdl script has long been a niche but powerful tool in the developer and data engineering community, primarily used for zero‑touch deployment and logging in distributed environments. The recent update pushed to its official GitHub repository marks a significant shift in its architecture, security model, and performance benchmarks.
For the uninitiated, zxdl stands for Zero‑Xfer Data Logger – a lightweight, cross‑platform utility that automates the extraction, transformation, and remote logging of system metrics or application events without requiring persistent agents on target machines. It is widely adopted in ephemeral container workflows, edge computing nodes, and air‑gapped environments where traditional logging agents (Fluentd, Logstash) are too heavy.
Where zxdl previously only emitted to a single URL or local file, the updated version supports multiple concurrent sinks: GitHub Actions and GitLab CI runners use zxdl
Example configuration snippet from the new zxdl.conf:
[sinks] primary = "https://logs.internal.corp:8443/v1/ingest" backup = "unix:///var/run/zxdl.sock" stdout_format = "json"
[retry] max_attempts = 5 backoff_base = 200 # milliseconds jitter = true
Solution: Use the new --random-delay flag: To use the updated cookie function:
./zxdl --random-delay 2,7 --input urls.txt
This introduces a 2-7 second random pause between requests.
This update modernizes the repository, improves reliability, and enhances usability. Key changes include: