Page Comparison

Elastic Protokolle werden in einem einen Thread geschrieben. Es ist nicht garantiert, dass die Ausführung erfogreich ist. Die Ablage und weitere Aktionen sind unabhängig möglich, auch wenn der ProtokolService offline ist.Die Konfiguration der Eigenschaften erfolgt über: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 ProtokolService is offline.

The configuration of the properties is done via:

<repo>.protocolservice.document.properties

...

 

<repo>.protocolservice.container.properties

Pro “Aktion“ muss ein Index erzeugt werden, es kann jeweils der selbe Index genutzt werden:

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

<repo>.protocolservice.elastic.index.

...

<action>=

...

Diese Aktionen müssen konfiguriert werden: create, read, update, delete, info.

Die verschiedenen Indexe können unterschiedliche Aufbewahrungszeiträume haben.

Soll sichergestellt werden, dass das Protokol geschrieben wird kann ein Fallback aktiviert werden. Dann weren alle Einträge lokal gecached.

...

<name>

These actions must be configured:

create, read, update, delete, info

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, elastic

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

...

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:

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 )