PingAccess

Log level category descriptions

The following table describes the fields available for managing log categories on the Log Settings page and within the /logSettings endpoint.

You can customize the log categories in both the admin console and the admin API by editing the log4j-categories.xml file directly. For more information, see the comments in the file.

Field Description Sensitive1

Core

Provides debug logging for core components.

No

Cluster Replication

Logs configuration replication details.

No

HTTP Request Headers

Logs HTTP request headers.

Yes

HTTP Request Parameters

Logs HTTP GET request parameters.

Yes

HTTP Client

Provides information about requests and responses that clients made to PingAccess.

Yes

HTTP Application

Provides information about requests and responses that PingAccess made to other tools or services.

Yes

Cookie

Logs both incoming and outgoing cookies.

No

Network Events

Analyzes the state of connections to PingAccess.

No

Configuration Management

Logs details related to loading the administrative configuration from the disk to the runtime.

No

CRL Handling

Logs certificate revocation checking and validation.

No

Groovy Rule

Logs information from within a groovy rule script.

No

API Audit

Logs API audit traffic, including requests and responses. This category is enabled by default.

No

Engine Audit

Logs engine audit traffic, including requests and responses. This category is enabled by default.

No

Agent Audit

Logs agent audit traffic, including requests and responses. This category is enabled by default.

No

Sideband Client Audit

Logs sideband client audit traffic, including requests and responses. This category is enabled by default.

No

Sideband Audit

Logs sideband client audit traffic, including requests and responses. This category is enabled by default.

No

1 Might log sensitive information if enabled