Loading

GitLab Integration

<div class="condensed-table">
| | |
| --- | --- |
| Version | 2.0.0 (View all) |
| Compatible Kibana version(s) | 8.13.0 or higher |
| Supported Serverless project types
What’s this? | Security
Observability |
| Subscription level
What’s this? | Basic |
| Level of support
What’s this? | Elastic |

</div>
This integration is for ingesting logs from GitLab.

  • api: Collect logs for HTTP requests made to the GitLab API
  • application: Collect logs for events in GitLab like user creation or project deletion.
  • audit: Collect logs for changes to group or project settings and memberships.
  • auth: Collect logs for protected paths abusive requests or requests over the Rate Limit.
  • pages: Collect logs for Pages.
  • production: Collect logs for Rails controller requests received from GitLab.
  • sidekiq: Collect logs from sidekiq for jobs background jobs that take a long time.

See the GitLab Log system docs for more information.

The GitLab module has been developed with and tested against the community edition version 16.8.5-ce.0.

Elastic Agent must be installed. For more details and installation instructions, please refer to the Elastic Agent Installation Guide.

There are several options for installing and managing Elastic Agent:

With this approach, you install Elastic Agent and use Fleet in Kibana to define, configure, and manage your agents in a central location. We recommend using Fleet management because it makes the management and upgrade of your agents considerably easier.

With this approach, you install Elastic Agent and manually configure the agent locally on the system where it’s installed. You are responsible for managing and upgrading the agents. This approach is reserved for advanced users only.

You can run Elastic Agent inside a container, either with Fleet Server or standalone. Docker images for all versions of Elastic Agent are available from the Elastic Docker registry, and we provide deployment manifests for running on Kubernetes.

Please note, there are minimum requirements for running Elastic Agent. For more information, refer to the Elastic Agent Minimum Requirements.

Refer to the GitLab documentation for the specific filepath(s) for your instance type. Both are provided as default in the configuration setup, but only one will be needed for use.

Collect logs for HTTP requests made to the GitLab API. Check out the GitLab API log docs for more information.

Collect logs for events happening in GitLab like user creation or project deletion. Check out the GitLab Application log docs for more information.

Collect logs for changes to group or project settings and memberships. Check out the GitLab Audit log docs for more information.

Collect logs for abusive protect paths requests or requests over the Rate Limit. Check out the GitLab Auth log docs for more information.

Collect logs for Pages. Check out the GitLab Pages log docs for more information.

Collect logs for Rails controller requests received from GitLab. Check out the GitLab production log docs for more information.

Collect logs from sidekiq for jobs background jobs that take a long time. Check out the GitLab sidekiq log docs for more information.