# Monitoring Boost provides multiple metrics for monitoring the services and APIs. All the metrics are emitted in Prometheus format and can be used to monitor and identify bottlenecks. The metrics endpoint for all Boost services is `/metrics`. The full list of metrics emitted by `boostd`, `booster-http` and `booster-bitswap` are [here](https://github.com/filecoin-project/boost/blob/main/metrics/metrics.go#L30-L90). The `boostd-data` (LID) metrics are separate from the other metrics and their list can be found [here](https://github.com/filecoin-project/boost/blob/main/extern/boostd-data/metrics/metrics.go#L28-L75). Apart from the prometheus metrics, all Boost services also provides tracing spans. These tracing spans can be useful to debug the bottleneck and low performance sections of the execution. You can enable tracing using `--tracing` flag. {% hint style="info" %} The default URL to export tracing is , which is not correct outside of a Kubernetes or docker environment. Users must set `--tracing-endpoint` flag to correct IP/Hostname pointing to their `tempo` instance. {% endhint %} By default, Boost ships a fully configured monitoring stack. This monitoring stack can be deployed on docker and allows storage provider to get started with monitoring in less than 10 minutes. We highly recommend using this stack to monitor your Boost services unless you are familiar with how to setup monitoring manually and create dashboards. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://boost.filecoin.io/monitoring.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.