Elasticsearch Connector Code Wiki
Elasticsearch Connector Code Wiki
Alto connector map
Elasticsearch at a glance
Distributed search and analytics engine for log data, full-text search, and observability
Page Summary
Understand what the Elasticsearch connector contributes and where to start implementation or review.
Tajo has catalog knowledge for this connector; runtime enablement depends on the API, MCP, or docs-only surface.
Normalize source data into stable Tajo objects, then activate it through Brevo contacts, events, lists, campaigns, or operational workflows.
Integration Profile
| Property | Value |
|---|---|
| Catalog status | OpenAPI |
| Runtime in Alto | Cataloged |
| Alto category | Search |
| Setup complexity | medium |
| Vendor docs | www.elastic.co/guide/en/elasticsearch/reference/current/rest-apis.html |
| Primary API host | Vendor-dependent |
| Last researched | 2026-04-12 |
System Shape
- Tajo authenticates against Elasticsearch using the available API, MCP, or documented integration surface.
- The connector reads source objects, events, and operational metadata from Elasticsearch.
- Tajo normalizes the records into stable external IDs and explicit sync resources.
- Brevo receives the activation layer: contacts, attributes, lists, transactional sends, campaign triggers, or CRM context.
- Logs, retries, and partial failures remain visible in Tajo so the integration can be operated safely.
Data Model
- Events, webhooks, and behavioral activity
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Implementation Map
| Area | What to verify |
|---|---|
| Authentication | Confirm scopes, token lifetime, revocation, and whether OAuth or API key auth is supported. |
| Pagination | Prefer cursor or updated-at pagination; document offset fallbacks and maximum page size. |
| Webhooks | Verify signature headers, replay windows, event IDs, and retry behavior before enabling live ingestion. |
| Rate limits | Capture vendor-specific retry headers and backoff policy in connector smoke tests. |
| Brevo mapping | Decide which fields become contact attributes, which records become events, and which actions trigger campaigns. |
Current Catalog Notes
Elastic publishes official OpenAPI spec in elasticsearch-specification repo.
API surface captured by Alto:
- Base URL or endpoint:
https://github.com/elastic/elasticsearch-specification/blob/main/output/openapi/elasticsearch-openapi.json - Documentation: Vendor docs
- Catalog source:
/home/ubuntu/alto/src/data/connectors.v2.ts
Tajo Review Checklist
- Does Elasticsearch have a verified auth path for production workspaces?
- Are primary resources mapped to stable external IDs?
- Is historical backfill separated from real-time webhook ingestion?
- Are retries idempotent for creates, updates, sends, and event ingestion?
- Are Brevo contact attributes, custom events, and campaign triggers named consistently?
- Are failure modes visible enough for an operator to resolve without reading code?