ElasticSearch Business Intelligence & Reporting

Knowi enables data discovery, query, aggregation, visualization and reporting automation from ElasticSearch along with other unstructured and structured datasources.


  1. Connect, extract and transform data from your ElasticSearch, using one of the following options:

    • Using our Cloud9Agent. This can securely pull data inside your network. See agent configuration for more details.
    • Through our UI to connect directly.
  2. Visualize and Automate your Reporting instantly.


If you are not a current Knowi user, check out our ElasticSearch Instant Reporting page to get started.


The following GIF image shows how to connect to ElasticSearch.

ElasticSearch Query

  1. Login to Knowi and select Settings -> Datasources from the left down menu.

  2. Click on ElasticSearch. Either follow the prompts to set up connectivity to your own ElasticSearch database, or, use the pre-configured settings into Cloud9 Chart's own demo ElasticSearch database.

    If you connecting through an agent, check Internal Datasource to assign it to your agent. The agent (running inside your network) will synchronize it automatically. Alternatively, configure datasource and queries directly into agent.

    When connecting from the UI directly to your ElasticSearch database, please follow the connectivity instructions to allow Knowi to access your database.

  3. Save the Connection. Click on the "Configure Queries" link on the success bar.

Queries & Reports

  1. Set up Query to execute.

    ElasticSearch Query

    Report Name: Specify a name for the report.

    ElasticSearch Query: Enter ElasticSearch queries. See ElasticSearch documentation for more details on their JSON based query syntax:

    Cloud9QL: Powerful SQL like post processor for the data returned by the ElasticSearch query. See Cloud9QL Docs for more details.

    Click 'Preview' to see the results.

  2. Warehousing strategy: By default, the results of the queries are stored into a flexible, scalable data warehouse. This provides an intermediary layer for your BI/reporting and provides advanced capabilities to store and incrementally track the data. Alternatively, if you want to execute the queries directly and bypass the warehouse to execute data directly, click on 'Direct Connection' option.

    If the warehousing mode is selected:

    • Specify how often the queries should be run. Select 'None' for a one time operation.
    • Overwrite Strategy: Overwrite Strategies determines how the data is stored in Knowi:

      i. If empty, data will be added on to the existing data for this dataset within Knowi. Or,

      ii. "All": Any existing data for this dataset will be replaced by this results.

      iii. One or More Field Names (Example: "A,B,C"): A new record is created where the values of the combination of the field names do not exist, and, updates current records for the field grouping where it exists. For example, if this is set to say "Date, Type", existing data with the same Date and Type values will be updated with the latest data, and new records created when they do not exist.

    • Click on 'Save' to complete setting up the report. This also sets up any query schedules, if configured.

    • Click on 'Dashboards' to access dashboards. You can drag and drop the newly created report from the widget list into to the dashboard.

Cloud9Agent Configuration

As an alternative to the UI based connectivity above, you can use Cloud9Agent inside your network to pull from ElasticSearch securely. See Cloud9Agent to download your agent along with instructions to run it.


  • Pull data using SQL.
  • Execute queries on a schedule, or, one time.

The agent contains a datasource_example_elasticsearch.json and query_example_elasticsearch.json under the examples folder of the agent installation to get you started.

  • Edit those to point to your database and modify the queries to pull your data.
  • Move it into the config directory (datasource_XXX.json files first if the Agent is running).

Datasource Configuration:

Parameter Comments
name Unique Datasource Name.
datasource Set value to elasticsearch
url URL to connect to, where applicable for the datasource. Example for ElasticSearch: localhost:3306/test
userId User id to connect, where applicable.
Password Password, where applicable
userId User id to connect, where applicable.

Query Configuration:

Query Config Params Comments
entityName Dataset Name Identifier
identifier A unique identifier for the dataset. Either identifier or entityName must be specified.
dsName Name of the datasource name configured in the datasource_XXX.json file to execute the query against. Required.
queryStr ElasticSearch query to execute. Required.
frequencyType One of minutes, hours, days,weeks,months. If this is not specified, this is treated as a one time query, executed upon Cloud9Agent startup (or when the query is first saved)
frequency Indicates the frequency, if frequencyType is defined. For example, if this value is 10 and the frequencyType is minutes, the query will be executed every 10 minutes
startTime Optional, can be used to specify when the query should be run for the first time. If set, the the frequency will be determined from that time onwards. For example, is a weekly run is scheduled to start at 07/01/2014 13:30, the first run will run on 07/01 at 13:30, with the next run at the same time on 07/08/2014. The time is based on the local time of the machine running the Agent. Supported Date Formats: MM/dd/yyyy HH:mm, MM/dd/yy HH:mm, MM/dd/yyyy, MM/dd/yy, HH:mm:ss,HH:mm,mm
c9QLFilter Optional post processing of the results using Cloud9QL. Typically uncommon against SQL based datastores.
overrideVals This enables data storage strategies to be specified. If this is not defined, the results of the query is added to the existing dataset. To replace all data for this dataset within Knowi, specify {"replaceAll":true}. To upsert data specify "replaceValuesForKey":["fieldA","fieldB"]. This will replace all existing records in Knowi with the same fieldA and fieldB with the the current data and insert records where they are not present.


Datasource Example:


Query Example:

        "entityName": "ElasticSearch Demo",
        "queryStr": "{\"size\":1000,\"query\": {\"query_string\": {\"query\": \"Transactional*\"}}} ",
        "c9QLFilter": "select sum(sent) as sent, sum(opened) as Opened, date(date) as Sent Date group by date(date)",
        "dsName": "demoElasticSearch",
        "overrideVals": {
            "replaceAll": true

The first query is run every 10 minutes at the top of the hour and replaces all data for that dataset in Knowi. The second is run once a day at 07:20 AM and updates existing data with the same Type field, or inserts new records otherwise.