All Collections
Data Push Destinations - Elasticsearch
Data Push Destinations - Elasticsearch

Send UXI data to your Elasticsearch Database

Written by Josh Peters
Updated over a week ago

Selecting the Elasticsearch destination will send your test result data or issue data to your Elasticsearch database. Each test result will be an elastic search document. The data will be sent from the UXI VPC located in AWS US-WEST-2. It is recommended to use either the Elasticsearch cloud database or use the Elasticsearch on AWS or some other cloud provider. If your Elasticsearch is on prem, it would require you to route the traffic accordingly. Elasticsearch 7.x is required.

Kibana: This destination requires you to create a Kibana user to access to read and write to the specified index. The Kibana user should only use basic auth.

Note that we have only tested the amazon elasticsearch service and the elasticsearch cloud.

To get started with the UXI Data Push Destination for Elasticsearch:

1. Create and start an Elasticsearch domain. Refer to the data estimate in the data push destination help article to size your Elasticsearch appropriately.

2. In Kabana, create a user for the UXI data push destination. Make sure the user has the role and permissions to monitor the cluster, create the index and read and write documents. Here is an example policy:



3. In the UXI dashboard, go to Settings > Integrations. In the Data Push Destinations section, click on the Add Destination button.

4. Select the following information from the Add Destination modal that appears:

  • Data Type: Test Results or Issues

  • Destination Type: Elasticsearch

  • Name: Give this integration a friendly name

  • URL: Enter the elastic search public URL

  • Username: Provide a username for the Elasticsearch user the data push destination will use to add documents

  • Password: Enter the password for the Elasticsearch user the data push destination will use to add documents

5. Click on the Add button.

Here is a short demo setting up the data push destination for elasticsearch

Did this answer your question?