This plugin keeps a log of who performed particular Jenkins operations, such as configuring jobs.
This plugin adds an Audit Trail section in the main Jenkins configuration page. On this page, you can configure log destination and settings (eg file size and number of rotating log files), and a URI pattern for requests to be logged. The default options select most actions with significant effect such as creating/configuring/deleting jobs and views or delete/save-forever/start a build. The log is written to disk as configured and recent entries can also be viewed in the Manage / System Log section.
Also see the JobConfigHistory Plugin for recording actual changes made to job configurations.
Output audit logs in rolling files.
The file logger relies on
java.util.logging.FileHandler and can use patterns to describe the log file location as documented here (
A separator can be set for the file logger in case further parsing of the file is done. Default separator is a space.
About the client IP-address appearing in the logs
The plugin uses a method that cannot guarantee that the actual IP of the client is captured. More details Be aware of this limitation, especially if your instance is configured behind a reverse proxy. For getting client IP-address correctly it’s required to set HTTP-header X-Forwarded-For on the reverse proxy side. Also follow these recommendations in order to get round this limitation.