About audit log policy profiles
To monitor activity and maintain compliance, you can apply audit log profiles that define the level of detail recorded for API server requests. While more comprehensive profiles provide request bodies for troubleshooting, they also increase resource overhead on the host system.
Audit log profiles define how to log requests that come to the OpenShift API server, Kubernetes API server, OpenShift OAuth API server, and OpenShift OAuth server.
{product-title} provides the following predefined audit policy profiles:
| Profile | Description | ||
|---|---|---|---|
|
Logs only metadata for read and write requests; does not log request bodies except for OAuth access token requests. This is the default policy. |
||
|
In addition to logging metadata for all requests, logs request bodies for every write request to the API servers ( |
||
|
In addition to logging metadata for all requests, logs request bodies for every read and write request to the API servers ( |
||
|
No requests are logged, including OAuth access token requests and OAuth authorize token requests. Custom rules are ignored when this profile is set.
|
-
Sensitive resources, such as
Secret,Route, andOAuthClientobjects, are only logged at the metadata level. OpenShift OAuth server events are only logged at the metadata level.
By default, {product-title} uses the Default audit log profile. You can use another audit policy profile that also logs request bodies, but be aware of the increased resource usage such as CPU, memory, and I/O.