Context provides a unified knowledge layer that connects services, infrastructure, tools, and documentation — enabling smarter alert investigations, faster root cause analysis, and more effective automation.

Whether you’re responding to an alert, running a task, or building a runbook, Context ensures that all the relevant metadata and supporting assets are just one click away.

​
✨ What Can You Do with Context?

  • Automatically map your services and infrastructure
  • Detect tools from alert data with zero config
  • Organize and manage documentation like RCAs and architecture overviews
  • Manually define and tag entities for full control
  • Link context to alerts, runbooks, and tasks

​
📁 Context Structure

Context is divided into two main sections:

​
1. Catalog

A live inventory of your environment, auto-synced from integrations and editable via UI.

  • Services
    Applications, APIs, or components identified from APM tools, CI/CD pipelines, or manually defined.

  • Infrastructure Resources
    Includes clusters, deployments, namespaces, node pools, and more from cloud providers or Kubernetes.

🔧 You can also manually create or edit catalog entries using the “Add New” option.

​
2. Resources

A knowledge base tied to your systems and teams.

  • Runbooks and Notes
    Debugging instructions, SOPs, and execution plans.

  • Documentation
    Postmortems, architecture files, onboarding guides — anything you need during incidents.

​
🧩 Where Is Context Used?

  • Alert Investigations
    Relevant context is surfaced automatically when viewing alert details.

  • Runbook Execution
    Context is referenced dynamically during automated and manual execution.

  • Search & Discovery
    Use the Context tab to browse or search across services, infra, tools, and documents.