The request-out log file pattern contains a list ofpipe ("|") separated values. The file pattern will contain the same number of columns, if a value is missing it will be empty.
Note: If not provided by the client, the 'Request Content-Length' value is initialised as "-1".
Request log file record structure
Timestamp | Trace ID | Remote Repository Name | Username | Request method | Request URL | Return Status | Request Content Length | Response Content Length | Request Duration
Request log file record sample
2021-05-12T13:58:46.686Z|40ea218a769325db|generic-remote|andreyt|HEAD|https://acme.jfrog.com/artifactory/generic-packages/jdbc-drivers/mssql-jdbc-7.4.1.jre11.jar|200|1219373|0|80
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 Repository Name | The name of the remote repository. |
|
Username | The requesting user's username or "anonymous" when accessed anonymously. |
|
Request method | The HTTP request method, in UPPERCASE. |
|
Remote URL | The URL for the remote resource. |
|
Return Status | The HTTP return code for the request. | 201 |
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. |