Administering Keen

Taiga

Chapter 19 of 30

Taiga

Taiga collection records the activity of chosen projects, so backlog and task work can stand as evidence.

Set KEEN_TAIGA_ENABLED and KEEN_TAIGA_BASE_URL; the token alias is TAIGA_TOKEN. Confirm the upstream account can read the intended projects.

Configure projects with project identifiers and optional labels, and inspect the project activity returned by the upstream identity before broadening the collection. Payloads retain the activity entry and recognised extracted values, which vary with the activity type.

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