Elasticsearch¶

Robusta actions can run in response to Elasticsearch/Kibana watchers by using Elasticsearch webhook actions.

A common use case is gathering troubleshooting data with Robusta when pods write specific error logs.

Robusta Configuration¶

1. The Robusta-relay must be enabled so that it can route Elasticsearch webhooks to the appropriate Robusta runner

2. The following variables must be defined in your generated_values.yaml file:

globalConfig:
  account_id: ""       # your official Robusta account_id
  signing_key: ""      # a secret key used to verify the identity of Elasticsearch

You do not define playbooks for Elasticsearch triggers in generated_values.yaml. Instead the playbook is defined entirely on the Elasticsearch side.

Example Elasticsearch Watcher¶

The following Elasticsearch Watcher configuration will trigger a Robusta playbook. Make sure you update <account_id>, <cluster_name>, and <secret_key> in the emphasized line. These should match the Robusta Helm chart values.