GitLab Logs
Connecting GitLab logs to your Panther Console
Overview
Panther supports onboarding GitLab logs using Data Transport mechanisms. Audit logs can be ingested with the HTTP Source, while other GitLab logs can be ingested with Amazon Web Services (AWS) S3 and SQS.
How to onboard GitLab Audit Streaming logs to Panther
This process outlines how to onboard GitLab Audit logs. To onboard other types of GitLab logs, such as API, Exceptions, Integrations, Git, and Production logs, follow the separate How to onboard non-Audit GitLab logs to Panther process below.
Step 1: Create an HTTP Source in Panther
In the left-hand navigation bar of your Panther Console, click Configure > Log Sources.
Click Create New.
Search for “GitLab,” then click its tile.
In the slide-out panel, the Transport Mechanism dropdown in the upper right corner will be pre-populated with the HTTP option.
Click Start Setup.

Follow Panther's instructions for configuring an HTTP Source, beginning at Step 5.
You will be required to use shared secret authentication. This is the only method of authentication GitLab supports.
The Header Name associated with your Secret Key Value will be locked with a value of
x-panther-gitlab.
Step 2: Set up Audit Log Streaming in GitLab.
In your GitLab console, navigate to your Group.
Click Security and Compliance > Audit Events.
In the tab at the top of the page, click Streams, then Add Streaming Destination.
Enter the information from the HTTP source you created in Step 1:
The URL provided by Panther.
The header name
x-panther-gitlaband the secret you configured in Panther.
Click Add to finish creating the Streaming Destination.
How to onboard non-Audit GitLab logs to Panther
The process below outlines how to onboard non-Audit GitLab logs to Panther, such as API, Exceptions, Git, Integrations, and Production logs. If you'd like to onboard Audit logs, follow the separate How to onboard GitLab Audit Streaming logs to Panther process above.
To connect these logs into Panther:
Log in to the Panther Console.
In the left sidebar, click Configure > Log Sources.
Click Create New.
Search for the log type you want to onboard, then click its tile.
Select the data transport method you wish to use for this integration, then follow Panther's instructions for configuring the method:
Configure GitLab to push logs to the Data Transport source.
See GitLab's documentation for instructions on pushing logs to your selected Data Transport source.
Supported log types
GitLab.API
Panther uses the latest version of GitLab API logs. Some fields differ from the official documentation.
Reference: GitLab Documentation on API JSON Logs.
GitLab.Audit
Multi-use schema for GitLab audit events, from both self-hosted audit log files and GitLab's audit event streaming feature.
For more information, see GitLab's documentation on Audit JSON Logs and GitLab's documentation on audit event streaming.
GitLab.Exceptions
GitLab log file containing changes to group or project settings
Reference: GitLab Documentation on Exceptions for JSON logs.
GitLab.Git
GitLab log file containing all failed requests from GitLab to Git repositories.
Reference: GitLab Documentation on Git for JSON Logs.
GitLab.Integrations
GitLab log with information about integrations activities such as Jira, Asana, and Irker services.
Reference: GitLab Documentation on Integrations for JSON Logs.
GitLab.Production
GitLab log for Production controller requests received from GitLab
Reference: GitLab Documentation on Production for JSON Logs.
Last updated
Was this helpful?

