---
title: HTTP request logging
description: HTTP requests to the runtime engine and the administrative console are logged to the <date>.request.log file and <date>.request2.log, respectively, by the Pingfederate web container.
component: pingfederate
version: 12.2
page_id: pingfederate:administrators_reference_guide:pf_http_request_loggin
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_http_request_loggin.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 5, 2022
superseded_by: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_http_request_loggin.html
---

# HTTP request logging

HTTP requests to the runtime engine and the administrative console are logged to the `<date>.request.log` file and `<date>.request2.log`, respectively, by the Pingfederate web container.

Like other PingFederate-generated log files, the HTTP request logs are written to the default PingFederate log directory. Properties controlling request logging are contained in the web-container configuration files:

* `jetty-runtime.xml` for the runtime engine (the `<date>.request.log` files)

* `jetty-admin.xml` for the administrative console (the `<date>.request2.log` files)

You can find these files in the `<pf_install>/pingfederate/etc` directory, and you can independently manage them on a per-server basis.