Tribal Knowledge Integration
Connect Slack, Notion, Confluence, Jira, Linear, and Glean and Kestrel will learn from your team's past incidents.
The hardest part of incident response isn't finding the fix - it's finding the context. That one Slack thread from 3am where the team debugged a VPC peering blackhole. The Notion runbook that documents exactly how to handle OOMKilled pods. The Jira ticket that explains why that specific security group rule exists.
Today, we're introducing Tribal Knowledge Integration - connecting Kestrel to the tools where your team's operational knowledge already lives.
What is Tribal Knowledge?
Tribal knowledge is the undocumented expertise that exists in your organization - the lessons learned from past incidents, the workarounds that senior engineers know by heart, the runbooks that never made it into formal documentation.
When Kestrel investigates an incident, it now searches your connected knowledge sources for relevant context, surfacing past solutions alongside its automated analysis.
Supported Integrations
We currently support the following knowledge sources:
- Slack- Search incident channels and threads for past debugging sessions
- Confluence- Index runbooks, post-mortems, and documentation
- Jira- Connect incident tickets and resolution notes
- Linear- Track engineering issues and their resolutions
- Glean- Unified search across your entire knowledge base
How It Works
When an incident is detected, Kestrel automatically searches your connected sources for relevant context. For example, if Kestrel detects an RDS instance running out of storage, it might surface:
- A Slack thread where your team resolved a similar storage exhaustion by enabling auto-scaling and purging old logs
- A Notion runbook documenting the RDS storage expansion and snapshot cleanup process
- A Linear ticket explaining why certain databases have stricter retention policies due to compliance requirements
This context is presented alongside Kestrel's automated investigation, giving you both real-time diagnostics and historical insight.
Getting Started
To connect your knowledge sources, navigate to Integrations → Tribal Knowledge in the Kestrel dashboard. Each integration uses OAuth or API tokens for secure access. Kestrel doesn't store any of your data - we use each tool's native search APIs to query your knowledge sources dynamically at investigation time.
For Slack users: if you've already connected the Kestrel Slack app, it will automatically be available as a tribal knowledge source.