Elasticsearch¶

The ELASTICSEARCH Action type allows you to extract data from a Tornado Action and send it to Elasticsearch.

The Elasticsearch Executor behind this Action type expects a Tornado Action to include the following elements in its payload:

An endpoint : The Elasticsearch endpoint which Tornado will call to create the Elasticsearch document (i.e. http://localhost:9200),
An index : The name of the Elasticsearch index in which the document will be created (e.g. tornado-example),

An data: The content of the document that will be sent to Elasticsearch

{
   "user" : "kimchy",
   "post_date" : "2009-11-15T14:12:12",
   "message" : "trying out Elasticsearch"
}

(optional) An auth: a method of authentication, see below

The Elasticsearch Executor will create a new document in the specified Elasticsearch index for each action executed; also the specified index will be created if it does not already exist.

In the above json document, no authentication is specified, therefore the default authentication method created during the Executor creation is used. This method is saved in a tornado configuration file (elasticsearch_executor.toml) and can be overridden for each Tornado Action, as described in the next section.

Elasticsearch authentication

When the Elasticsearch Action is created, a default authentication method can be specified and will be used to authenticate to Elasticsearch, if not differently specified by the action. On the contrary, if a default method is not defined at creation time, then each action that does not specify an authentication method will fail.

To use a specific authentication method the action should include the auth field with either of the following authentication types: None or PemCertificatePath, like shown in the following examples.

None: the client connects to Elasticsearch without authentication

Example:
```
{
   "type": "None"
}
```
PemCertificatePath: the client connects to Elasticsearch using the PEM certificates read from the local file system. When this method is used, the following information must be provided:
- certificate_path: path to the public certificate accepted by Elasticsearch
- private_key_path: path to the corresponding private key
- ca_certificate_path: path to CA certificate needed to verify the identity of the Elasticsearch server
Example:
```
{
   "type": "PemCertificatePath",
   "certificate_path": "/path/to/tornado/conf/certs/tornado.crt.pem",
   "private_key_path": "/path/to/tornado/conf/certs/private/tornado.key.pem",
   "ca_certificate_path": "/path/to/tornado/conf/certs/root-ca.crt"
}
```