The request log file pattern contains a list of pipe ("|") separated values. The file pattern will contain the same number of columns, if a value is missing it will be empty.
If not provided by the client, the 'Request Content-Length' value is initialised as "-1".
Request log file record structure
Timestamp | Trace ID | Remote Address | Username | Request method | Request URL | Return Status | Request Content Length | Response Content Length | Request Duration | Request User Agent
Request log file record sample
2018-11-18T15:39:04.902Z|d5d75b3c41242768|127.0.0.1|anonymous|GET|api/v1/cert/root|200|0|6|0|JFrog Access Java Client/4.1.12
Warning
The request log information is not indicative of your data transfer usage. You can view your data transfer usage in My Usage in MyJFrog and Enable Detailed Data Transfer Logs in MyJFrog to view detailed data transfer logs.
The following table lists the request log values and their descriptions.
Value | Description | Example |
|---|---|---|
Timestamp | The date and time the request was completed and entered into the log file, in UTC time with the standard format: [yyyy-MM-dd'T'HH:mm:ss.SSSZ]. |
|
Trace ID | The trace id value. |
|
Remote Address | The IP address of the remote caller (ipv4 or ipv6). |
|
Username | The requesting user's username or "anonymous" when accessed anonymously. |
|
Request method | The HTTP request method, in UPPERCASE. |
|
Request URL | The relative URL for the request. |
|
Return Status | The HTTP return code for the request. |
|
Request Content Length | The size of the user request in bytes, for example, the size of an uploaded file. -1 if unknown. | |
Response Content Length | The size of the server response in bytes, for example, the size of downloaded file. -1 if unknown (for example, chunked encoding). | |
Request Duration | The time in ms for the request to process. | |
Request User Agent | The request user agent. |
|