Elasticsearch

Elasticsearch

Certified
Enterprise Edition

Tasks that push Kestra data to Elasticsearch clusters for search and analytics.

Use these tasks to bulk-export execution logs into a target index via Elasticsearch’s REST API. Configure hosts (with scheme/port), optional basic auth and headers, and tune bulk chunk size to balance throughput and memory.

How to use the Elasticsearch EE plugin

Ship Kestra execution logs to Elasticsearch from Kestra flows.

Authentication

Set connection.hosts (required, list of Elasticsearch endpoints including scheme and port, e.g. https://elasticsearch.com: 9200). Authenticate via connection.basicAuth.username and connection.basicAuth.password, or pass a custom Authorization header via connection.headers. Optionally set connection.pathPrefix (for clusters behind a proxy), connection.trustAllSsl (accept self-signed certificates), connection.strictDeprecationMode (treat deprecation warnings as errors), and connection.targetServerVersion (default 8; set to 9 for Elasticsearch 9 clusters). Store secrets in secrets and apply connection properties globally with plugin defaults.

Log exporters

LogExporter ships execution logs to Elasticsearch via the Bulk API — set connection and indexName (both required). Optionally set chunk (logs per bulk request, default 1000).