epok

Promtail / Loki push compatibility

Use grafana/promtail:3.4.2. The Loki push endpoint accepts Promtail’s Snappy protobuf and JSON streams. Real-agent acceptance awaits the deployment and rig run. Set EPOK_INGEST_KEY in the process environment and start Promtail with -config.expand- env=true and -config.file pointing to this file.

Configuration

yaml
server:
  http_listen_port: 9080
  grpc_listen_port: 0
positions:
  filename: /tmp/p2-promtail-positions.yaml
clients:
  - url: https://ingest.getepok.dev/loki/api/v1/push
    headers:
      X-API-Key: ${EPOK_INGEST_KEY}
    batchwait: 1s
scrape_configs:
  - job_name: p2-promtail
    static_configs:
      - targets: [localhost]
        labels:
          service: p2-promtail
          __path__: /var/log/promtail.log

Keep your ingest key private. Missing keys return 401; unknown keys return 403. A successful HTTP response alone is not proof of stored data.

Real-agent acceptance

The real-agent acceptance row is pending the deployment and rig run. It requires the exact unique file line and service p2-promtail in the key’s workspace and project. Promtail sends its native payload directly to the ingest endpoint.

From a source checkout with Docker Compose, run the isolated acceptance rig. It uses a fresh key and run marker, publishes no host ports, and removes its stack on exit. Every required stored-data check must pass.

bash
scripts/p2_agent_acceptance.sh

Vector JSON logs · All install guides