Administering Keen
GitLab
Chapter 16 of 30
GitLab
GitLab collection records the project activity of chosen groups or users.
Set KEEN_GITLAB_ENABLED=true, KEEN_GITLAB_BASE_URL and GITLAB_TOKEN, using an upstream identity with read access to the intended projects.
Add groups using a group ID or full path, or users using a username or numeric ID. Group discovery includes accessible subgroup projects. Initial collection looks back 14 days, followed by saved cursors.
Avoid overlapping scopes. Identities are tracked per collection scope, so overlapping user and group collections can retain the same activity more than once. Inspect per-project runner results to identify permissions and discovery failures.
Inspect and map evidence
Inspect a collected event and use Create mapping from this event. Structured selectors expose the payload that this source actually returns; a useful starting path is activity. Action and outcome filters use Keen's normalised event values. Preview matching and non-matching examples.
For file-managed deployments, collection inputs live in config/gitlab.yml. See the common collection workflow for UI configuration and override behaviour.