Jenkins Audit Logs Integration

Send Jenkins Audit Logs to Realm

This guide walks you through connecting Jenkins audit logs to Realm using the Audit Trail plugin. The integration uses a syslog push approach — Jenkins streams audit events in RFC 5424 format directly to a Realm Collector running in your environment, which forwards them through your data pipeline to your configured destination.

Prerequisites

1. Active Jenkins instance with administrator access.
2. Access to the Realm Security console.
3. A Realm Collector deployed and reachable from your Jenkins server. See the Realm Collector install guide for setup instructions.
4. The Audit Trail plugin installed on your Jenkins instance (Manage Jenkins > Plugins > Available plugins, search for Audit Trail).

Configure the Integration in Realm

1. Log in to the Realm console.
2. Go to Sources > Add and create a new Source.

   Name: Jenkins Audit
   Format: Jenkins Audit

3. Go to Collectors and select your existing Collector, or go to Collectors > Add to create one.
4. Click Add Stream on the Collector.

   Product Format: Jenkins Audit
   Port: Select a unique port or use the Realm-generated port.
   Source: Jenkins Audit

5. Click Add Stream.
6. Note the Collector's IP address (or hostname) and the port assigned to the Jenkins Audit stream — you will enter these into the Jenkins Audit Trail plugin in the next section.

Configure the Audit Trail Plugin in Jenkins

1. In Jenkins, go to Manage Jenkins > System.
2. Scroll to the Audit Trail section.
3. Under Loggers, click Add Logger and select Syslog Logger.
4. Configure the Syslog Logger:

   Syslog Host: <Realm Collector IP or hostname>
   Syslog Port: <port noted from Realm Collector stream>
   Message Format: RFC 5424
   App Name: Jenkins (or another identifier meaningful to your environment)
   Facility: USER (or another facility appropriate to your environment)

5. Click Save.

Jenkins will now forward audit events — including user actions, job triggers, configuration changes, and credential access — to your Realm Collector in RFC 5424 syslog format.

Verifying Delivery

Once the plugin is configured, perform a test action in Jenkins (e.g. trigger a build or update a configuration). Then verify ingestion in the Realm console by checking the activity on the Jenkins Audit stream in your Collector.

Note: For more details on the Audit Trail plugin and the events it captures, refer to the Jenkins Audit Trail plugin documentation.

Support

If you encounter any issues or require assistance, contact Realm Security support.