Administering Keen
BookStack
Chapter 20 of 30
BookStack
BookStack collection captures chosen wiki pages, so a published policy or procedure can stand as evidence of itself.
Set KEEN_BOOKSTACK_ENABLED, KEEN_BOOKSTACK_BASE_URL, BOOKSTACK_TOKEN_ID and BOOKSTACK_TOKEN_SECRET. Browse the server-backed book and page catalogue in the editor, choose pages and configure capture options; imported selectors can continue to identify pages by book, slug, title or pattern. The same selection is available through Policies & processes when the ingester is enabled.
Check the captured content and section handling before relying on a policy extract as evidence.
Payloads include bookstack → page_id, page_slug, page_title, book_slug and preview information. Select the actual nested JSON path shown on the event.
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 bookstack → page_slug. 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/bookstack.yml. See the common collection workflow for UI configuration and override behaviour.