You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Otherwise, consult the Quarkus documentation for the full list of variables that can be used.
17403
+
Otherwise, consult the Quarkus documentation for the full list of variables that can be used. Note that enabling the `%++{++ALL_REQUEST_HEADERS++}++` attribute directly or with a `long` named format introduces a risk of sensitive header values being logged.
17404
+
17405
+
HTTP `Authorization` header value is always masked. Use the `masked-headers()` property to mask other sensitive headers.
The TTL of the hash slot cache. A hash slot cache is used by the clustered Redis client to prevent constantly sending `CLUSTER SLOTS` commands to the first statically configured cluster node.
81340
+
The TTL of the topology cache. A topology cache is used by a clustered Redis client and a sentinel Redis client to prevent constantly sending topology discovery commands (`CLUSTER SLOTS` or `SENTINEL ...`).
81297
81341
81298
-
This setting is only meaningful in case of a clustered Redis client and has no effect otherwise.
81342
+
This setting is only meaningful in case of a clustered Redis client and a sentinel Redis client and has no effect otherwise.
|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-all-config[icon:question-circle[title=More information about the Duration format]]
The TTL of the hash slot cache. A hash slot cache is used by the clustered Redis client to prevent constantly sending `CLUSTER SLOTS` commands to the first statically configured cluster node.
81970
+
The TTL of the topology cache. A topology cache is used by a clustered Redis client and a sentinel Redis client to prevent constantly sending topology discovery commands (`CLUSTER SLOTS` or `SENTINEL ...`).
81927
81971
81928
-
This setting is only meaningful in case of a clustered Redis client and has no effect otherwise.
81972
+
This setting is only meaningful in case of a clustered Redis client and a sentinel Redis client and has no effect otherwise.
|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-all-config[icon:question-circle[title=More information about the Duration format]]
The TTL of the hash slot cache. A hash slot cache is used by the clustered Redis client to prevent constantly sending `CLUSTER SLOTS` commands to the first statically configured cluster node.
496
+
The TTL of the topology cache. A topology cache is used by a clustered Redis client and a sentinel Redis client to prevent constantly sending topology discovery commands (`CLUSTER SLOTS` or `SENTINEL ...`).
497
497
498
-
This setting is only meaningful in case of a clustered Redis client and has no effect otherwise.
498
+
This setting is only meaningful in case of a clustered Redis client and a sentinel Redis client and has no effect otherwise.
|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-quarkus-redis-client_quarkus-redis[icon:question-circle[title=More information about the Duration format]]
The TTL of the hash slot cache. A hash slot cache is used by the clustered Redis client to prevent constantly sending `CLUSTER SLOTS` commands to the first statically configured cluster node.
1126
+
The TTL of the topology cache. A topology cache is used by a clustered Redis client and a sentinel Redis client to prevent constantly sending topology discovery commands (`CLUSTER SLOTS` or `SENTINEL ...`).
1127
1127
1128
-
This setting is only meaningful in case of a clustered Redis client and has no effect otherwise.
1128
+
This setting is only meaningful in case of a clustered Redis client and a sentinel Redis client and has no effect otherwise.
|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-quarkus-redis-client_quarkus-redis[icon:question-circle[title=More information about the Duration format]]
The TTL of the hash slot cache. A hash slot cache is used by the clustered Redis client to prevent constantly sending `CLUSTER SLOTS` commands to the first statically configured cluster node.
496
+
The TTL of the topology cache. A topology cache is used by a clustered Redis client and a sentinel Redis client to prevent constantly sending topology discovery commands (`CLUSTER SLOTS` or `SENTINEL ...`).
497
497
498
-
This setting is only meaningful in case of a clustered Redis client and has no effect otherwise.
498
+
This setting is only meaningful in case of a clustered Redis client and a sentinel Redis client and has no effect otherwise.
|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-quarkus-redis-client_quarkus-redis[icon:question-circle[title=More information about the Duration format]]
The TTL of the hash slot cache. A hash slot cache is used by the clustered Redis client to prevent constantly sending `CLUSTER SLOTS` commands to the first statically configured cluster node.
1126
+
The TTL of the topology cache. A topology cache is used by a clustered Redis client and a sentinel Redis client to prevent constantly sending topology discovery commands (`CLUSTER SLOTS` or `SENTINEL ...`).
1127
1127
1128
-
This setting is only meaningful in case of a clustered Redis client and has no effect otherwise.
1128
+
This setting is only meaningful in case of a clustered Redis client and a sentinel Redis client and has no effect otherwise.
|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-quarkus-redis-client_quarkus-redis[icon:question-circle[title=More information about the Duration format]]
Otherwise, consult the Quarkus documentation for the full list of variables that can be used.
66
+
Otherwise, consult the Quarkus documentation for the full list of variables that can be used. Note that enabling the `%++{++ALL_REQUEST_HEADERS++}++` attribute directly or with a `long` named format introduces a risk of sensitive header values being logged.
67
+
68
+
HTTP `Authorization` header value is always masked. Use the `masked-headers()` property to mask other sensitive headers.
0 commit comments