To configure log forwarding to an external source, you can use the Permit Logs Forwarder. (1) Currently, Permit supports forwarding logs to ElasticSearch and stdout of the FluentBit container. Enabling the Logs Forwarder Use the PDP's values.yaml and configure the following: 1. Switch

pdp.logs_forwarder.enabled

to

true

. 2. Set the

pdp.logs_forwarder.type

to the desired log forwarder type,

elasticsearch

or

stdout

. 3. ​*If you choose ElasticSearch:*​ • Set

pdp.logs_forwarder.elasticsearch.host

to the desired ElasticSearch host. • Set

pdp.logs_forwarder.elasticsearch.port

to the desired ElasticSearch port. • Set

pdp.logs_forwarder.elasticsearch.index

to the desired ElasticSearch index. • Set

pdp.logs_forwarder.elasticsearch.cloud_auth

to the desired ElasticSearch username and password as

{user}:{password}

. 4. ​*Optional:*​ Set

pdp.logs_forwarder.debug_mode

to

true

to enable debug logs of the FluentBit container. How It Works Once

pdp.logs_forwarder.enabled

is set to true, the logs will be forwarded to the desired log forwarder type by FluentBit sidecar container. The PDP container will save the logs to

/tmp/pdp.log

file, and the FluentBit sidecar container will read the logs from this file, filtering the Decision Logs and forward them to the desired log forwarder type. The Log Forwarder allows you to forward logs from the PDP to any observability platform, such as Elasticsearch, OpenTelemetry, or any other service. (2)

To learn more, see the sources I considered: [[1] Logs Forwarder](https://docs.permit.io/how-to/use-audit-logs/logs-forwarder) [[2] Permit.io Launch Week - Day 5: Fine-Tuned Performance](https://www.permit.io/blog/launch-week-5-performance)