Markdown upload

Markdown upload context enriches an existing Pulse. It does not create Pulses.

How this helps triage: matching excerpts can show up in the summary, the first checks, and What informed this on the Pulse.

Upload tenant-scoped markdown playbooks when no docs platform connector exists. During triage, Exhale scores heading sections and attaches the top matches (breadcrumb plus score), falling back to a truncated whole document.

Connect

1. Sign in as a workspace admin.
2. Open Connections → Context → Runbooks & docs → Markdown upload.
3. Upload markdown files and map them to service names or alert keys.
4. Test connection to mark the connector configured.

Missing credentials, timeouts, or vendor 403s skip this block. Triage still completes. Send-test-alert Pulses skip live collectors.

Plan

Markdown upload is available on all plans and does not consume Context connector slots (it uses a separate runbook document cap).

Connector slots are shared across Context categories (markdown runbooks use a separate document cap). Tighten AI → Prompt → Context use if excerpts are noisy or too large.

API

Writes use the signed-in session and CSRF. Secrets are never returned on GET.

Related

• Context index
• Prompt → Context use