Route gateway audit logs to Loki

Post http-log to /customers instead of /logs. Fluent Bit's http input derives the
record tag from the request URI, so the path is what identifies this domain
in the collector and becomes the Loki label domain=customers.

The collector keeps writing every domain to the on-disk audit trail as
well, so this is reversible by restoring the previous path.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Stéphane Tailland
2026-08-25 07:25:43 +02:00
parent 3b20b0a35b
commit d0093ad2c7
+3 -1
View File
@@ -29,7 +29,9 @@ spec:
BACKEND_AUDIENCE: '["classic-models-api"]' BACKEND_AUDIENCE: '["classic-models-api"]'
BACKEND_SCOPES: '[]' BACKEND_SCOPES: '[]'
API_RATE_LIMIT_MINUTE: "60" API_RATE_LIMIT_MINUTE: "60"
AUDIT_LOG_ENDPOINT: http://audit-log-collector.observability.svc.cluster.local/logs # The URI path is the collector's routing key: Fluent Bit tags the
# record `customers` and turns that into the Loki label domain=customers.
AUDIT_LOG_ENDPOINT: http://audit-log-collector.observability.svc.cluster.local/customers
REST_HOSTNAME: customers-dev.sttlab.local REST_HOSTNAME: customers-dev.sttlab.local
TOKEN_EXCHANGE_CLIENT_ID: kong-token-exchange-broker TOKEN_EXCHANGE_CLIENT_ID: kong-token-exchange-broker
# Unused today — same dead variable already present in catalog-api's # Unused today — same dead variable already present in catalog-api's