Access Log

Artifactory maintains an access log containing all security-related events, their source IP and context. Events include information on accept/reject of logins, and download, browsing and deployment of artifacts.

The access log is located at $JFROG_HOME/artifactory/var/log/artifactory-access.log.

You can also view and download the access log from the Artifactory UI. In the Administration module go to Artifactory | System Logs.

Artifactory access log.jpg

An access log record has the following structure:

<timestamp> [<trace-id>] [<response> <action>] <repository-key>:<path> for client : <username> / <ip> [<authentication-type>]

The repository path and the authentication type are omitted when the event doesn't include them.

Here is a typical example:

2024-04-09T22:48:09.057Z [23805d42fe9d707e] [ACCEPTED DOWNLOAD] maven-remote-cache:org/iostreams/iostreams/0.2/iostreams-0.2.jar for client : anonymous / 86.12.14.192 [token]

The following table describes the fields in an access log record.

Log FieldDescription
Timestamp (UTC)The date and time the message was logged, in UTC, with the format yyyy-MM-dd'T'HH:mm:ss.SSSZ based on RFC-3339.
Trace IDThe Trace ID is used to identify a request across services.
Action response and typeThe response, ACCEPTED or DENIED, and the action. Actions include ANNOTATE, DOWNLOAD, DEPLOY, DELETE, SEARCH, LOGIN, CONFIGURATION_CHANGE, CREATE, UPDATE, APPROVE, FORM_SUBMIT, PROPERTY_ADDED, PROPERTY_REMOVED, PROPERTY_UPDATED, BUILD_CREATE, BUILD_PROMOTE, and BUILD_DELETE.
Repository pathThe repository key and artifact path, separated by a colon. This field is omitted when the event doesn't access an artifact, such as a login.
UsernameThe accessing user's username, or anonymous when accessed anonymously. A denied login can record the username as NA.
IPThe accessing user's IP address.
Authentication typeThe authentication type in use, token or apiKey. This field is omitted when the event doesn't record an authentication type, including a denied login.

You can also choose to receive focused information about events for a specific repository section, using Watches .


Did this page help you?