Gitlab
Logs Collected
There are various logs that can be collected and sent to Stackdriver Logging using the BlueMedora BindPlane Log Agent:
- Application Logs
- Production Logs
- API Logs
- Sidekiq Logs
- Shell Logs
These logs provide, when coupled with Stackdriver Logging, provide visibility into events that have occurred, such as user creation. Information related to tasks being processed in the background, requests being made directly to the API, Gitlab shell information, and Rails controller requests made from Gitlab are all included.
Here are a few example screenshots of logs being displayed in Stackdriver Logging


Gitlab Application Logs Example


Gitlab Production Logs Example


Gitlab API Logs Example


Gitlab Sidekiq Logs Example


Gitlab Shell Logs Example
Log Collection Setup
Follow these steps to setup log collection for Varnish.
Pre-requisites
- Locate the path to the Gitlab Rails Application Log files
- Locate the path to the Gitlab Rails Production Log files
- Locate the path to the Gitlab Rails API Log files
- Locate the path to the Gitlab Rails Sidekiq Log files
- Locate the path to the Gitlab Shell Log files
Configure a Gitlab Source
- Install the BindPlane Log Agent on the host system.
- Login to BindPlane and select the Logs tab.


Logs Tab
- Select the Sources tab.


Sources Tab
- In the top-right portion of the screen, click on the Add Source Configuration button


Add Source Configuration Button
- Choose Gitlab
- Fill out the Gitlab log configuration options.


Gitlab Log Configuration Form
Updated over 2 years ago