GitLab Add-On
Overview
Details
Installation
Installation is as standard for a Splunk Add-On
Set-up
This input requires your GitLab token (Obtained via GitLab > Profile Settings > Access Tokens) for authentiction. When setting up inputs, you have the option to enter a project ID or not.
PLEASE NOTE
If you do not specify a specific project ID, you will only get event data associated with the account the token is associated with.
Using Data
The add-on will collect any new information gathered since last run. This is done by storing the datetime of last run in the KV Store and then passing it into GitLab as a HTTP Param. The add-on focusses on the events, initially retrieving these before getting records associated with the event (Merge Requests, Project Info, Commits, Milestones...). During retrieval, it will then store everything in Splunk in JSON format.
Troubleshooting
Please check you have the correct permissions should you not be getting any data into Splunk. The splunkd sourcetype in the _internal index may assist with confirming any access issues.
Setting the logging level to debug is also advised if you encounter any issues as this should hopefully give you an idea as to where the problems lie. If you still are struggling, please get in touch or go to answers.splunk.com for more info. Should you need to get in touch, please supply a copy of the internal log, including the error line with MsgID should one exist.
Release Notes
Version 1.0.2
Resolve API Issue