1a40961d62
* initial commit; fixed anchor links on internal docs pages * add back in absolute paths for links in code comments * fix: update linkchecker include filter to match server port 1314 PR #1629 changed the Hugo server to port 1314 but forgot to update the --include filter, which still matched port 1313. This caused all links to be excluded, making the checker a no-op (0 checked, 82277 excluded). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Fix url rewrite regex so images are not impacted * Fix links from non-documentation pages * Fix broken links * more broken links * more broken links * broken link * Add srcset width descriptor to .lycheeignore * Ignore URLs that contain a % character * Anchor regex so it matches the entire URL --------- Co-authored-by: kanungle <neil.kanungo@gmail.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
2.5 KiB
title
| title |
|---|
| Datadog |
Datadog is a cloud-based monitoring and analytics platform that offers real-time monitoring of servers, databases, and numerous other tools and services. It provides visibility into the performance of applications and enables businesses to detect issues before they affect users.
You can install the Qdrant integration to get real-time metrics to monitor your Qdrant deployment within Datadog including:
-
The performance of REST and gRPC interfaces with metrics such as total requests, total failures, and time to serve to identify potential bottlenecks and mitigate them.
-
Information about the readiness of the cluster, and deployment (total peers, pending operations, etc.) to gain insights into your Qdrant deployment.
Usage
- With the Datadog Agent installed, run the following command to add the Qdrant integration:
datadog-agent integration install -t qdrant==1.0.0
- Edit the
conf.d/qdrant.d/conf.yamlfile in your Agent's configuration directory to start collecting your Qdrant metrics.
Most importantly, set the openmetrics_endpoint value to the /metrics endpoint of your Qdrant instance.
instances:
## @param openmetrics_endpoint - string - optional
## The URL exposing metrics in the OpenMetrics format.
- openmetrics_endpoint: http://localhost:6333/metrics
If the Qdrant instance requires authentication, you can specify the token by configuring extra_headers.
# @param extra_headers - mapping - optional
# Additional headers to send with every request.
extra_headers:
api-key: <QDRANT_API_KEY>
-
Restart the Datadog agent.
-
You can now head over to the Datadog dashboard to view the metrics emitted by the Qdrant check.