View HTTP Access Logs for the Pulse UI Service

Pulse supports HTTP access logging for the ad-pulse-ui service to capture requests received by Pulse UI. These logs provide information about HTTP requests, client addresses, authenticated users, response status codes, and GraphQL operations.

HTTP access logs help administrators monitor application activity, investigate request failures, and meet security auditing requirements.

Pulse generates an access log entry for every HTTP request, including requests for static assets such as JavaScript files, CSS files, and images. As a result, HTTP access logging can generate a large volume of log entries.

Configure HTTP Access Logging

HTTP access logging is enabled by default for the ad-pulse-ui service. The default value of the LOG_LEVEL environment variable is info. No additional configuration is required.

To change the logging level, update LOG_LEVEL under the ad-pulse-ui service in $AcceloHome/config/docker/ad-core.yml.

HTTP Access Log Fields

Each access log entry contains the following fields in a predefined order.

Field	Description
Client address	IP address of the client or intermediary that connects directly to the server. If Pulse is accessed through an ingress controller, load balancer, or proxy, this field contains the intermediary's IP address.
Identity marker	Reserved field containing -.
User	Username of the authenticated user. Displays - if the user is not authenticated.
Request	HTTP method, requested URI, query string (if present), and HTTP version. For example, GET /path?x=1 HTTP/1.1. Supported sensitive query parameter values are replaced with REDACTED.
Result code	HTTP response status code indicating whether the request succeeded, failed, or was redirected.
Size	Size of the HTTP response.
Referring page	URL of the referring page, if available. Otherwise, displays -.
Browser/client info	Browser or application that initiated the request, as identified by the User-Agent header.
Forwarded-from address	Address information provided through the X-Forwarded-For header, if available.
Operation name	Name of the GraphQL operation for requests to /graphql. For batched requests, operation names are separated by commas. Displays - for other requests or when unavailable.
Operation type	Type of GraphQL operation (query or mutation) for requests to /graphql. Displays - for other requests or when unavailable.
Group/tenant	Customer environment, group, or cluster associated with the request.
Request ID	Unique identifier associated with the request for tracing and troubleshooting.
Duration	Time taken to process the request, in milliseconds.
Completion status	Indicates whether the response completed normally or the connection was interrupted.
Category marker	Fixed value http_access that identifies the entry as an HTTP access log. This is always the last field in the log entry.

Note:

Fields without values are represented by -, including the identity marker, user, referring page, and other optional fields.

The X-Forwarded-For header is recorded separately from the client address because its value can be modified by the requesting client or intermediate systems.

Sensitive Information Redaction

Pulse redacts sensitive query parameter values from the Request field before recording an HTTP access log entry.

Redaction applies only to the query string and the following parameter names (case-insensitive):

password, passwd, pwd, token, jwt, access_token, refresh_token, apikey, api_key, secret, key, licensekey, and authorization.

When a matching parameter is detected, Pulse replaces its value with REDACTED.

Important

Redaction is limited to the specified query parameters in the Request field. It does not guarantee the removal of sensitive information from other fields or request content. Avoid including credentials or other sensitive information in request URLs.