Elastic

Elastic 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.

Exhale uses Elastic credentials at triage time to attach cluster health and Observability excerpts.

This is not Kibana alert webhook ingest. If Elastic alerts should become Pulses, connect Sources → Elastic.

Connect

1. Sign in as a workspace admin.
2. Open Connections → Context → Observability context → Elastic.
3. Save the Elastic public HTTPS host and API key, then Test connection.
4. Test connection to mark the connector configured.

See Elastic's official guide: Elasticsearch API keys.

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

Plan

Growth or higher.

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 log lines and deep links attach when the key has the needed scopes.

Related

• Context index
• Prompt → Context use