Bindplane

The Bindplane Developer Hub

Welcome to the Bindplane developer hub. You'll find comprehensive guides and documentation to help you start working with Bindplane as quickly as possible, as well as support if you get stuck. Let's jump right in!

Logs Collected

The logs collected are pulled directly from the /var/log/jenkins/jenkins.log file on Linux and MacOS. Windows differs in that there are two files for the logs:

  • %JENKINS_HOME%/jenkins.out and %JENKINS_HOME%/jenkins.err

The log files contain all the relevant and useful information related to the Jenkins server. Using the Blue Medora BindPlane Log Agent, the logs can be collected and sent directly to Stackdriver Logging for further use. Below is an example of the Jenkins logs within Stackdriver Logging!

Jenkins Logs Example

Log Collection Setup

Follow these steps to setup log collection for Jenkins.

Pre-requisites

  • Locate the path to the Jenkins log files

Linux & MacOS Default: /var/log/jenkins/jenkins.log
Windows Default: %JENKINS_HOME%/jenkins.out and %JENKINS_HOME%/jenkins.err

Configure a Jenkins Source

  1. Install the BindPlane Log Agent on the host system.
  2. Login to BindPlane and select the Logs tab.

Logs Tab

  1. Select the Sources tab.

Sources Tab

  1. In the top-right portion of the screen, click on the Add Source Configuration button

Add Source Configuration Button

  1. Choose Jenkins
  2. Fill out the Jenkins log configuration options.

Jenkins Log Configuration Form

Updated about a year ago

Jenkins


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.