Access Logging

Structured JSON logging with sampling; logs 10% of requests. request_id ensures each log line has a correlation ID. access_log emits method, path, status, and timing

Category: Practical
Task: Structured JSON logging with sampling; logs 10% of requests. request_id ensures each log line has a correlation ID. access_log emits method, path, status, and timing

Prerequisites: The product runtime and any backend services referenced by this configuration.

Run it: Use ghcr.io/praxis-proxy/praxis:0.7.2 and follow the first reverse-proxy tutorial to mount and start the configuration.

This configuration comes from the selected release. The example has not been run here; external services are not bundled.

Download the source file.

# Access Logging
#
# Structured JSON logging with sampling; logs ~10% of
# requests.
# request_id ensures each log line has a correlation ID.
# access_log emits method, path, status, and timing.
#
# Enable with RUST_LOG=info to see log output.
#
listeners:
  - name: default
    address: "127.0.0.1:8080"
    filter_chains:
      - main

filter_chains:
  - name: main
    filters:
      - filter: request_id

      - filter: access_log
        sample_rate: 0.1

      - filter: router
        routes:
          - path_prefix: "/"
            cluster: backend

      - filter: load_balancer
        clusters:
          - name: backend
            endpoints:
              - "127.0.0.1:3000"

insecure_options:
  allow_private_endpoints: true # example proxies to local backends