Skip to main content

Overview

IncidentFox uses RAPTOR (Recursive Abstractive Processing for Tree-Organized Retrieval), a state-of-the-art hierarchical knowledge system based on ICLR 2024 research. This enables handling 100+ page runbooks without context loss.

Why RAPTOR?

Traditional RAG (Retrieval Augmented Generation) struggles with:

Architecture

Knowledge Types

RAPTOR organizes knowledge into abstraction levels:

Adding Knowledge

Via API

Via Slack

Via Web UI

  1. Navigate to Knowledge Base > Add Knowledge
  2. Paste or upload content
  3. Tag with services and categories
  4. Submit for processing

Document Sources

IncidentFox can ingest knowledge from:

Confluence Integration

Knowledge Graph

Beyond tree structure, RAPTOR maintains a knowledge graph:

Relationships

Querying the Graph

Learning from Investigations

IncidentFox automatically learns from successful investigations:

Pattern Recording

After each investigation:
  1. Extracts cause-solution pairs
  2. Tags with services and symptoms
  3. Stores in knowledge base
  4. Increases confidence with repetition

Example Pattern

Finding Similar Investigations

IncidentFox searches for:
  • Similar symptoms
  • Same services
  • Related error patterns

Importance Scoring

RAPTOR uses 9+ signals to rank knowledge relevance:

Configuration

RAPTOR Settings

Retrieval Settings

API Endpoints

Retrieve Knowledge

Get Answer with Sources

Provide Feedback

Tree Statistics

Returns:
  • Total documents
  • Tree depth
  • Node counts by level
  • Last sync time

Best Practices

Document Quality

  • Keep runbooks up to date
  • Include specific commands and thresholds
  • Add examples and expected outcomes
  • Tag with relevant services

Feedback Loop

  • Provide feedback on retrieved knowledge
  • Flag outdated information
  • Suggest improvements

Service Tagging

Tag all knowledge with:
  • Service name
  • Environment (prod, staging)
  • Category (runbook, alert, architecture)

Troubleshooting

Knowledge Not Retrieved

  1. Check document is indexed: GET /api/v1/kb/status
  2. Verify tagging and metadata
  3. Check relevance threshold settings

Stale Knowledge

  1. Set up automatic sync from sources
  2. Configure freshness decay
  3. Regularly review and update

Next Steps

How It Works

See RAPTOR in the full architecture

Configuration

Configure knowledge settings