From 8c6f23fafe72fde87ed8816f924e3fa7d4caccec Mon Sep 17 00:00:00 2001 From: timvisee Date: Tue, 4 Feb 2025 11:00:51 +0100 Subject: [PATCH] Bump configuration file --- .../content/documentation/guides/configuration.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/qdrant-landing/content/documentation/guides/configuration.md b/qdrant-landing/content/documentation/guides/configuration.md index 5e4a193d7..ea4cfab4b 100644 --- a/qdrant-landing/content/documentation/guides/configuration.md +++ b/qdrant-landing/content/documentation/guides/configuration.md @@ -126,17 +126,18 @@ The following YAML example describes the available configuration options. ```yaml log_level: INFO -# Configures the format of log lines, supported formats are `text` (default) and `json` -log_format: text - # Logging configuration # Qdrant logs to stdout. You may configure to also write logs to a file on disk. # Be aware that this file may grow indefinitely. # logger: +# # Logging format, supports `text` and `json` +# format: text # on_disk: # enabled: true # log_file: path/to/log/file.log # log_level: INFO +# # Logging format, supports `text` and `json` +# format: text storage: # Where to store all the data @@ -422,6 +423,12 @@ service: # # jwt_rbac: true + # Hardware reporting adds information to the API responses with a + # hint on how many resources were used to execute the request. + # + # Uncomment to enable. + # hardware_reporting: true + cluster: # Use `enabled: true` to run Qdrant in distributed deployment mode enabled: false