krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-04 10:28:29 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add audit logging documentation for cluster configuration

Browse Source
This commit is contained in:
Bastian Hofmann
2026-04-02 10:11:41 +02:00
parent 110d52048c
commit 79cb01ce41
1 changed files with 45 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/cloud/configure-cluster.md
+45 -1
View File
@@ -9,7 +9,7 @@ Qdrant Cloud offers several advanced configuration options to optimize clusters
The cloud platform does not expose all [configuration options](/documentation/operations/configuration/) available in Qdrant. We have selected the relevant options that are explained in detail below.
In addition the cloud platform automatically configures the following settings for your cluster to ensure optimal performance and reliability:
In addition, the cloud platform automatically configures the following settings for your cluster to ensure optimal performance and reliability:
* The maximum number of collections in a cluster is set to 1000. Larger numbers of collections lead to performance degradation. For more information see [Multitenancy](/documentation/manage-data/multitenancy/).
* Strict mode is activated by default for new collections enforcing that all filters being used in retrieve and update queries are indexed. This improves performance and reliability. You can disable this individually for each collection. For more information see [Strict Mode](/documentation/operations/administration/#strict-mode).
@@ -89,3 +89,47 @@ You can add labels to a Qdrant Cluster from the cluster's detail page. Labels ar
![Cluster Labels](/documentation/cloud/cloud-cluster-labels.png)
## Audit Logs
You can activate audit logs for your cluster in the cluster configuration tab of the cluster details page. Audit logs provide a record of all API calls made to the cluster. This is useful for security and compliance purposes.
Audit logs are available for all paid clusters, starting with Qdrant v1.17.0; the download endpoint starting with Qdrant v1.17.1.
The following information is tracked:
* The performed action (e.g. `list_collections`, `create_collection`, `upsert_points`, etc.)
* The timestamp of the action
* The API key ID used to perform the action, or the User ID if the action was performed through the Web UI
* The result of the action (success or failure)
* The IP address from which the action was performed
You can configure the rotation (daily/hourly) and the retention of the log files (how many of the rotated log files should be kept). The audit log files will be stored on your encrypted database storage disk. You need to ensure that you have enough storage capacity available. The storage capacity and usage is reported in your cluster metrics.
You can download the audit logs through the Qdrant API:
```sh
curl -X POST 'https://node-N-YOUR-CLUSTER-URL:6333/audit/logs' \
-H 'api-key: QDRANT_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"limit": 50,
"time_from": "2026-03-26T00:00:00Z",
"time_to": "2026-03-27T00:00:00Z",
"filters": {
"result": "denied",
"collection": "my_collection"
}
}'
```
Or without a filter:
```sh
curl -X POST 'https://node-N-YOUR-CLUSTER-URL:6333/audit/logs' \
-H 'api-key: QDRANT_API_KEY' \
-H 'Content-Type: application/json' \
-d '{}'
```
Note that each cluster node will only return the audit logs for the actions that were performed on that specific node. If you have a multi-node cluster, you need to query the [node specific URLs](/documentation/cloud/cluster-access/#node-specific-endpoints) separately to get the complete audit log for the cluster.