> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/automate-protect-and-extend/integrations-and-apis/prometheus-exporter.md). # VergeOS Prometheus Exporter (ioMetrics) The VergeOS Prometheus Exporter collects metrics from VergeOS environments and exposes them in Prometheus format for monitoring vSAN tiers, clusters, and nodes. ## Overview The VergeOS Exporter is a monitoring tool that collects metrics from your VergeOS environment and exposes them in Prometheus format. It provides visibility into VSAN tiers, clusters, and nodes, enabling comprehensive monitoring of your VergeOS infrastructure. ## Key Features * Collection of VSAN tier metrics for storage performance monitoring * Cluster-wide metrics to understand distributed performance * Node-level metrics for detailed infrastructure analysis * Easy integration with Prometheus and compatible monitoring systems ## Documentation and Resources For installation instructions, usage examples, configuration options, and a complete list of available metrics, or to open up issues you're experiencing with the Exporter please visit the official GitHub repository: ## Support If you encounter issues or have feature requests, please open an issue on the GitHub repository ## Additional Resources * [Prometheus Documentation](https://prometheus.io/docs/introduction/overview/) * [Grafana Documentation](https://grafana.com/docs/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.verge.io/automate-protect-and-extend/integrations-and-apis/prometheus-exporter.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.