/
Protocol Elastic Search (tC)

Protocol Elastic Search (tC)

Elastic logs are written in a single thread. Taking into account that it is not guaranteed that the execution is successful. Filing and further actions are possible independently, even if the Protocol Service is offline.

The configuration of the properties is done via see Protocol Service for possible values:

<repo>.protocolservice.document.properties <repo>.protocolservice.container.properties <repo>.protocolservice.additional.properties

 

One index must be created per "action", the same index can be used each time:

<repo>.protocolservice.elastic.index.<action>=<name>

 

These actions must be configured:

create, read, update, delete, info, admin, unknown, query, supplementary

The different indexes may have different retention periods.

If you want to ensure that the log is written, a fallback can be enabled. Then all entries are cached locally

 

Configuration parameters in repository.cfg, elasticv2

<repoName>.protocolservice.type=elasticv2 <repoName>.protocolservice.elasticv2.host = http://127.0.0.1:9200 <repoName>.protocolservice.elasticv2.index.create = protocol-fi <repoName>.protocolservice.elasticv2.index.read = protocol-fi <repoName>.protocolservice.elasticv2.index.update = protocol-fi <repoName>.protocolservice.elasticv2.index.delete = protocol-fi <repoName>.protocolservice.elasticv2.index.info = protocol-fi <repoName>.protocolservice.elasticv2.index.admin = protocol-fi <repoName>.protocolservice.elasticv2.index.unknown = protocol-fi #<repoName>.protocolservice.elasticv2.authentication.type= #default: none #<repoName>.protocolservice.elasticv2.authentication.credentials= #default: #<repoName>.protocolservice.elasticv2.maxconnections= #default: 50 #<repoName>.protocolservice.elasticv2.connecttimeout= #default: 5 #<repoName>.protocolservice.elasticv2.sockettimeout= #default: 30 #<repoName>.protocolservice.elasticv2.requesttimeout= #default: 10 #<repoName>.protocolservice.elasticv2.fallback.type= #default:

Notes for Elastic 8

Starting with version 8. By default when starting the Elastic server Security and HTTPS is enabled. This may be useful, but for local testing it’s rather a hindrance.
It can be deactivated by editing the file: config/elasticsearch.yml, adding the following entries:

 

xpack.security.enabled: false xpack.security.transport.ssl.enabled: false xpack.security.http.ssl.enabled: false

(Source citation: https://discuss.elastic.co/t/cannot-disable-security-in-8-1/299857 )