Elasticsearch

3DS Server and 3DS Server Admin application can be configured to use Elasticsearch to store and search transaction logs history. Using Elasticsearch as a log storage instead of SQL is advised in case of high number of incoming transactions.

Advantages of using Elasticsearch

  • Text search - faster search time than SQL databases
  • Transaction logs can be accessed through Kibana, which will give flexibility for evaluating and aggregation of the transaction information.
  • Elasticsearch is a common service on major cloud providers and can be easily configured.

Compatibility

Elasticsearch Java Client with version 8.7.1 is used. The client is forward compatible; meaning that the client supports communicating with greater or equal minor versions of Elasticsearch Server.

Configuration

The following sections give an overview of the Elasticsearch configuration required for both 3DS Server and 3DS Server Admin applications. Please see the Properties page for the 3DS Server and 3DS Server Admin for more details.

3DS Server Configuration

With the following configuration the 3DS Server will store incoming transaction logs in Elasticsearch.

  • threedss.logging.storage.type property must include elasticsearch. The property can accept multiple values.
  • spring.elasticsearch.uris property must point to running Elasticsearch server. (ex. http://localhost:9200/)

3DS Admin Configuration

With the following configuration the 3DS Admin application will use the Elasticsearch storage for searching the transaction logs in the Admin UI.

  • threedss.transaction-logs.search.source must have value elasticsearch. The property can accept only one value.
  • spring.elasticsearch.uris property must point to running Elasticsearch server. (ex. http://localhost:9200/)