Choose a forwarding method
This page helps you choose how logs should reach logging24. It is intentionally a decision page, not a full option reference.
Recommendation
The recommended production path for Linux environments is the native Linux binary forwarder. If you want a general CLI workflow that also covers historical imports, use
l24
.
| Linux Binary | Recommended for production Linux servers. Best fit for long-running service-based forwarding. |
| l24 CLI | Cross-platform forwarding and imports. Best when you want one tool for live ingest and backfills. |
| Syslog/TLS | Use when you already have rsyslog-style forwarding infrastructure. |
| Heroku | Use for Heroku log drain integrations. |
| Promtail / Loki | Migration or compatibility path for existing Loki-oriented setups. |
| Python | Application-level integration path when you need direct Python logging integration. |
Which path fits your situation?
Production Linux host
Use Linux Binary . It is the primary recommended operational path and is the best place to start for systemd-managed production forwarding.
Cross-platform setup or quick manual ingest
Use
l24 CLI
. It covers live forwarding via
l24 forward
and historical backfills via
l24 import
.
Existing infrastructure you do not want to replace
Use the integration guide that matches your current estate: Syslog/TLS , Heroku , Promtail / Loki , or Python .
Token requirement
All forwarding methods require a write token. See
Authentication Tokens
for secure token handling via
env://
,
file://
, or direct token input.
Detailed references
After forwarding is in place, continue to Querying to learn how the data is searched, or jump to Web UI if you want an interactive way to explore the data first.