Promtail / Loki compatibility

This path exists for teams that already have Promtail or Loki-oriented shipping in place. It is best treated as a migration or compatibility route, not the primary recommendation for new Linux deployments.

When to use this

You already run Promtail and want to keep that configuration model.
You are migrating away from a Loki backend and want to minimize ingest-side changes.
You need a compatibility bridge while moving toward a different logging24-native setup.

Recommended alternative for new setups

For new Linux production deployments, prefer Linux Binary . For general CLI-based workflows, prefer l24 CLI .

Endpoint

Use the Loki-compatible push endpoint under ingest.logging24.com:9200 .

Promtail example

server:
  http_listen_port: 9080
  grpc_listen_port: 0

clients:
  - url: http://ingest.logging24.com:9200/loki/api/v1/push

scrape_configs:
  - job_name: system
    static_configs:
      - targets:
          - localhost
        labels:
          job: syslog
          __path__: /var/log/syslog

Headers and organization metadata

If your compatibility setup needs extra headers, add them through the Promtail client configuration:

clients:
  - url: http://ingest.logging24.com:9200/loki/api/v1/push
    headers:
      X-Scope-OrgID: your-org-id

Migration notes

Start by changing only the push target, then validate that logs arrive as expected.
Keep label design intentional so that the resulting search experience still maps cleanly to your logging24 prefixes and workflows.
Plan a later move to a logging24-native forwarding path if you want a simpler long-term operational model.