From e6d0cb105f0df87284d2a3a5969ed8aa6cbe7f77 Mon Sep 17 00:00:00 2001 From: mmattel Date: Tue, 4 Apr 2023 08:52:00 +0200 Subject: [PATCH] added userlog redis sentinel info --- services/userlog/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/services/userlog/README.md b/services/userlog/README.md index b7c5ff758d..41d0dd339f 100644 --- a/services/userlog/README.md +++ b/services/userlog/README.md @@ -20,6 +20,7 @@ The `userlog` service persists information via the configured store in `USERLOG_ 1. Note that in-memory stores are by nature not reboot persistent. 2. Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`. These settings are blank by default which means that the standard settings of the configured store applies. 3. The userlog service can be scaled if not using `in-memory` stores and the stores are configured identically over all instances. +4. When using `redis-sentinel`, the Redis master to use is configured via `USERLOG_STORE_ADDRESSES` in the form of `:/` like `10.10.0.200:26379/mymaster`. ## Configuring