budiprihhastomo / djelas-audit-trail-plugin

Audit Trail Plugin With Added Some Features

Audit Trail Plugin

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.

Logger Configuration

File logger

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 (%h, %g…​).

A separator can be set for the file logger in case further parsing of the file is done. Default separator is a space.

Syslog logger

Send audit logs to a Syslog server.

Console logger

Output audit logs in stdout or stderr. Primarily intended for debugging purpose.

Elastic Search logger

Send audit logs to an Elastic Search server

Other configuration

Log build triggers

Will log the cause of a build. Defaults to true.

Log credential users

Will log usage of credentials as long as they are consumed through the Credentials plugin. Defaults to true.

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.

Changelog

From version 2.5 on, changelog is automatically generated using release-drafter. See directly the GitHub release page for the plugin.

For older releases, have a look to the archive.