Jump to: navigation, search

elasticsearch-<data-source-id> Section



  

Data source–specific configuration sections enable you to specify Elasticsearch connections for different types of data that could be stored in an Elasticsearch database and retrieved by Genesys Info Mart.

By default, the Genesys Info Mart application template includes the [elasticsearch-sdr0] section and options, for specifying the Elasticsearch cluster that Genesys Info Mart uses to retrieve Session Detail Record (SDR) data in environments with Genesys Designer. (Support for Genesys Designer is available in certain Genesys Cloud implementations.)

If you want Genesys Info Mart to process data that a particular data source stored in an Elasticsearch database and make this data available in the Info Mart database for downstream reporting applications, add the applicable configuration section(s) and options on the Options tab of the Genesys Info Mart Application object. Name the section [elasticsearch-<data-source-id>], where <data-source-id> matches the name of the data source that Genesys Info Mart supports.

Each data source–specific configuration section can contain the following option.


client

Default Value: None
Valid Values: off or any valid location of the cluster node(s) of the Elasticsearch cluster, properly formatted
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.009.20

This option specifies one or more nodes in the Elasticsearch cluster that Genesys Info Mart uses to retrieve data from an Elasticsearch database version 5.0 or higher. Genesys Info Mart uses the REST API client to communicate with the Elasticsearch cluster. You must specify the REST API URL address(es) for the REST client in the following format:

  • rest(http://<es-node>:<port>[,http://<es-node>:<port>]*)

g:tenant-prefix

Default Value: No default value
Valid Values: A string identifying the tenant on a shared Elasticsearch cluster
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.011.15

In Cloud deployments, the option defines a Cloud tenant prefix for Elasticsearch indexes on an Elasticsearch cluster shared across multiple Cloud tenants. The tenant prefix enables Genesys Info Mart to identify Elasticsearch indexes related to the particular Cloud tenant.

If specified, the option value overrides the index-pattern and index-regexp values from the XML source metadata, and the tenant prefix is included in index pattern and regexp strings.

Example

The following table illustrates the effect of specifying a tenant prefix, where the source type is sdr and the source ID is sdr0.

[elasticsearch-sdr0].g:tenant-prefix index-pattern index-regexp
Not defined ‘sdr’-yyyy.MM.dd sdr-*
-my-tenant ’sdr-my-tenant’-yyyy.MM.dd sdr-my-tenant-*

sources:extra

Default Value: None
Valid Values: A comma-separated list of any valid identifiers (IDs) of the data sources for the Elasticsearch database
Changes Take Effect: On the next ETL cycle
Dependencies: None
Introduced: 8.5.011.14

In an environment where a single Elasticsearch database stores data from multiple sources, this option enables you to configure a number of data sources in a single section. Specify the ID of the main data source as the suffix in the section name, such as sdr1 in elasticsearch-sdr1. Specify IDs of any additional data sources as a comma-separated list in the option value. Do not list an ID for the same data source more than once, whether explicitly or implicitly. For example, for Genesys Info Mart to retrieve the data that sdr1, ocs1, and ocs2 data sources store on node1 of the ElasticSearch cluster, add the following configuration:

Example:

[elasticsearch-sdr1]
sources:extra=ocs1,ocs2
client=rest(http://node1:9200)

When multiple elasticsearch-* sections are configured, ensure unique reference to a given data source ID across all the sections, to avoid an InvalidConfiguration exception and a failure of the ElasticSearch step and transformation job. For instance, specifying the sdr2 data source twice, as in the example below, one time in a dedicated section and the other as an additional data source, is treated as incorrect configuration.

Incorrect configuration:
[elasticsearch-sdr1]
sources:extra=sdr2
client=rest(http://node1:9200)
[elasticsearch-sdr2]
client=rest(http://node2:9200)

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on June 11, 2018, at 11:04.