Jump to Content

BindPlane Documentation

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

1876 — Gitlab Application Logs Example

1876 — Gitlab Application Logs Example

1872 — Gitlab Production Logs Example

1872 — Gitlab Production Logs Example

1872 — Gitlab API Logs Example

1872 — Gitlab API Logs Example

1870 — Gitlab Sidekiq Logs Example

1870 — Gitlab Sidekiq Logs Example

1874 — Gitlab Shell Logs Example

1874 — 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.

284 — Logs Tab

284 — Logs Tab

Select the Sources tab.

249 — Sources Tab

249 — Sources Tab

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

576 — Add Source Configuration Button

576 — Add Source Configuration Button

Choose Gitlab
Fill out the Gitlab log configuration options.

514 — Gitlab Log Configuration Form

514 — Gitlab Log Configuration Form

Updated about 3 years ago