Configuration Overview

Configuration Model

IncidentFox uses a hierarchical configuration system that allows organizations to set defaults while enabling teams to customize their specific needs.

Hierarchy

Configuration flows from top to bottom. Each level can:

Inherit settings from parent levels
Override specific settings
Add additional configuration

How Merging Works

When IncidentFox loads a team’s configuration, it:

Starts with organization defaults
Deep-merges each intermediate group’s config
Deep-merges the team’s config
Returns the final “effective config”

Deep merge means nested objects are merged recursively, not replaced entirely. Arrays are typically replaced, not concatenated.

Example

Organization Config:

{
  "mcp_servers": ["grafana", "aws"],
  "agents": {
    "investigation_agent": {
      "prompt": "You are an SRE investigation agent for Acme Corp..."
    }
  },
  "feature_flags": {
    "enable_auto_mitigation": false
  }
}

Team Config (Platform Team):

{
  "mcp_servers": ["grafana", "aws", "coralogix"],
  "agents": {
    "investigation_agent": {
      "enable_extra_tools": ["snowflake", "custom-runbooks"]
    }
  }
}

Effective Config for Platform Team:

{
  "mcp_servers": ["grafana", "aws", "coralogix"],
  "agents": {
    "investigation_agent": {
      "prompt": "You are an SRE investigation agent for Acme Corp...",
      "enable_extra_tools": ["snowflake", "custom-runbooks"]
    }
  },
  "feature_flags": {
    "enable_auto_mitigation": false
  }
}

Configuration Sections

Core Settings

Field	Type	Description
`team_name`	string	Display name (immutable at team level)
`slack_channel`	string	Default Slack channel for notifications
`slack_group_to_ping`	string	Group to mention (e.g., `@oncall-platform`)

Agent Configuration

Configure behavior for each agent type:

{
  "agents": {
    "investigation_agent": {
      "prompt": "Custom system prompt...",
      "enabled": true,
      "disable_default_tools": ["shell"],
      "enable_extra_tools": ["custom-tool"]
    }
  }
}

See Agent Configuration for details.

Tool Configuration

Enable/disable and configure tools:

{
  "tools": {
    "kubernetes": {
      "enabled": true,
      "default_namespace": "production"
    },
    "coralogix": {
      "enabled": true,
      "api_key": "vault://secrets/coralogix-api-key"
    }
  }
}

See Tool Configuration for details.

MCP Servers

Configure Model Context Protocol servers:

{
  "mcp_servers": ["grafana", "aws", "custom-server"]
}

Knowledge Sources

Configure where agents look for documentation and runbooks:

{
  "knowledge_source": {
    "grafana": ["prod-k8s", "prod-logs"],
    "google": ["drive:folder/oncall-runbooks"],
    "confluence": ["space:SRE"]
  }
}

Feature Flags

Control feature behavior:

{
  "feature_flags": {
    "enable_auto_mitigation": false,
    "enable_write_actions": true,
    "require_approval": true
  }
}

Alerts Configuration

Customize alert handling:

{
  "alerts": {
    "disabled": ["cpu_throttle_high", "disk_pressure"]
  }
}

Managing Configuration

Via Web UI

Log in to your IncidentFox dashboard
Navigate to Team Console > Configuration
Edit settings in the visual editor
Save changes (may require approval if enabled)

Via API

# Get effective config
curl -X GET https://api.incidentfox.ai/api/v1/config/me/effective \
  -H "Authorization: Bearer $TEAM_TOKEN"

# Update team config
curl -X PUT https://api.incidentfox.ai/api/v1/config/me \
  -H "Authorization: Bearer $TEAM_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "mcp_servers": ["grafana", "aws", "coralogix"]
  }'

Viewing Raw Lineage

To understand why a setting has a particular value:

curl -X GET https://api.incidentfox.ai/api/v1/config/me/raw \
  -H "Authorization: Bearer $TEAM_TOKEN"

Returns:

{
  "lineage": ["org-root", "engineering-group", "platform-team"],
  "configs": {
    "org-root": { /* org config */ },
    "engineering-group": { /* group config */ },
    "platform-team": { /* team config */ }
  }
}

Audit Trail

All configuration changes are logged. View the audit history:

curl -X GET https://api.incidentfox.ai/api/v1/config/me/audit \
  -H "Authorization: Bearer $TEAM_TOKEN"

Returns:

[
  {
    "version": 5,
    "changed_at": "2024-01-15T10:30:00Z",
    "changed_by": "user@company.com",
    "diff": {
      "mcp_servers": {
        "old": ["grafana", "aws"],
        "new": ["grafana", "aws", "coralogix"]
      }
    }
  }
]

Best Practices

Start broad, refine narrow - Set sensible defaults at the org level, then let teams customize as needed.

Use org-level defaults for common settings
Group by function - Platform teams vs. application teams may need different configs
Minimize team overrides - Only override what’s truly team-specific
Use vault references for secrets - Never store credentials in plain text
Enable approval workflows for production teams

Getting Started

Core Concepts

Configuration

Integrations

Data Sources

Tools Catalog

Configuration Overview

Configuration Model

Hierarchy

How Merging Works

Example

Configuration Sections

Core Settings

Agent Configuration

Tool Configuration

MCP Servers

Knowledge Sources

Feature Flags

Alerts Configuration

Managing Configuration

Via Web UI

Via API

Viewing Raw Lineage

Audit Trail

Best Practices

Next Steps

Agent Configuration

Tool Configuration

​Configuration Model

​Hierarchy

​How Merging Works

​Example

​Configuration Sections

​Core Settings

​Agent Configuration

​Tool Configuration

​MCP Servers

​Knowledge Sources

​Feature Flags

​Alerts Configuration

​Managing Configuration

​Via Web UI

​Via API

​Viewing Raw Lineage

​Audit Trail

​Best Practices

​Next Steps

Agent Configuration

Tool Configuration

Configuration Model

Hierarchy

How Merging Works

Example

Configuration Sections

Core Settings

Agent Configuration

Tool Configuration

MCP Servers

Knowledge Sources

Feature Flags

Alerts Configuration

Managing Configuration

Via Web UI

Via API

Viewing Raw Lineage

Audit Trail

Best Practices

Next Steps