Administering Keen

Gitea

Chapter 15 of 30

Gitea

Gitea collection records repository activity for chosen users or organisations, or the entries of a repository feed.

Enable and authenticate

Set KEEN_GITEA_ENABLED=true, KEEN_GITEA_BASE_URL and GITEA_TOKEN. The default GITEA_AUTH_MODE is token; feed authentication can also use GITEA_USERNAME or GITEA_COOKIE where the selected mode requires it.

Select users, organisations or feeds

Under Sources & evidence mapping, open this source and choose Add collection: users with the account login, organizations with the organisation login, or feeds with a specific repository feed URL.
Run a collection and inspect an actual event before choosing field paths. Repository activity is stored under activity; feed records can use rss.

A mapping that matches all source events does not create a collection. If the runner reports no configured inputs, add a collection and run it again.

Going deeper: discovery and lookback

User discovery covers repositories owned by that user; discovery repeats on each run and uses the token's visibility. Initial API activity collection looks back 14 days, subject to the upstream history available, and later runs use saved cursors. Each named connection supplies its own endpoint and credentials; add repository or feed inputs to the appropriate connection.

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/gitea.yml. See the common collection workflow for UI configuration and override behaviour.