Elasticsearch

Index a new document into an Elasticsearch index with a specified ID or auto-generated key.

Permanently remove a document from an Elasticsearch index by its ID, keeping your index clean and your storage costs in check.

Fetch a single document from an Elasticsearch index by its exact ID, returning the full source body in milliseconds.

Retrieve every document in an Elasticsearch index (up to the configured size limit), ideal for full-index audits or small working sets.

Apply a partial or full update to an existing Elasticsearch document by ID, changing only the fields you specify without re-indexing the whole source.

Create a new Elasticsearch index with custom settings and mappings, ready to receive documents from the first write.

Drop an entire Elasticsearch index and all its documents permanently, used for cleanup after migrations or test runs.

Retrieve the settings, mappings, and aliases for a specific Elasticsearch index, letting you inspect its configuration programmatically.

List every index in the Elasticsearch cluster with their health, document count, and storage size in one call.

Execute a full-text or structured Elasticsearch query against an index and return matching documents with relevance scores in milliseconds.

Write hundreds or thousands of documents to an Elasticsearch index in a single batched API call, avoiding the overhead of per-document round-trips.

Add new fields or adjust analyzer settings on an existing Elasticsearch index mapping without requiring a full re-index.

Execute an Elasticsearch aggregation — terms, date histogram, average, percentiles — to compute analytics over indexed documents without moving data to a separate BI tool.

Attach a named alias to one or more Elasticsearch indices, enabling zero-downtime index swaps and simplified query routing.

Poll the Elasticsearch cluster health API to retrieve overall status (green/yellow/red), active shards, and pending tasks.

Fires when a new document is successfully written to an Elasticsearch index; can be scoped to a specific index name.

Fires when an existing document's fields are modified via update or partial update; scoped to a specific index.

Fires when a document is removed from an index by ID, enabling downstream cleanup and audit-trail updates.

Fires when a new index appears in the cluster, useful for auto-configuring ILM policies or aliases on freshly provisioned indices.

Fires when a search request is submitted against a monitored index, enabling latency tracking and query-pattern analytics.

Fires when an index transitions between green, yellow, and red health states, enabling proactive alerting before data loss occurs.

Fires when Elasticsearch begins moving shards between nodes, signalling a rebalance, node join, or node failure event.