Based on the available sources, I don't have specific documentation about configuring the PDP's log output format for GCP Logs compatibility. The deployment guide for GCP Cloud Run (1) covers container configuration, environment variables, and health checks, but doesn't address log formatting for GCP's log severity detection. The sources do mention that the PDP uses various logging components internally (2) (3) (4) (5) , but don't provide configuration options to change the log output format to match GCP's expected severity levels. To help investigate this further, could you provide: 1. Which Workspace / Project / Env you are using 2. What calls are you performing (as SDK code or CURL) 3. Which PDP version you are running 4. Relevant logs from your PDP showing the severity mismatch This will help our engineers investigate whether there's a configuration option or if this requires a fix on Permit's end. ​*Potential workarounds to explore:*​ • Check if GCP Logs allows custom severity parsing rules for your log stream • Consider using a log processing layer (like Fluent Bit) between the PDP and GCP Logs to transform the severity levels • Review if there are any PDP environment variables related to log formatting (though none are documented in the available sources)

To learn more, see the sources I considered: [[1] Deploying PDP on GCP Cloud Run](https://docs.permit.io/how-to/deploy/cloud-hosts/gcp-cloud-run) [[2] Unable to push the policy data since OPA is not ready yet in sidecar pattern](https://github.com/permitio/PDP/issues/266) [[3] Secure data is being logged](https://github.com/permitio/opal/discussions/575) [[4] Logging mode can't be changed by accessor function](https://github.com/permitio/fastapi_websocket_rpc/issues/56) [[5] LOGURU mode logging doesn't work.](https://github.com/permitio/fastapi_websocket_rpc/issues/57)