> 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/run-the-platform/maintenance-and-monitoring/diagnostics-overview.md).

# VergeOS Diagnostics Overview

Overview of diagnostic tools in VergeOS, including component-specific diagnostics for networks, nodes, vSAN, and NAS, plus system-wide tools like subscriptions and Prometheus integration.

VergeOS provides comprehensive diagnostic tools integrated throughout the platform to help system administrators monitor, troubleshoot, and maintain optimal performance across all virtualization components.

## Component-Specific Diagnostics

* **Network Diagnostics**

  Network infrastructure troubleshooting and performance analysis

  **Access:** Networks → \[Select Network] → Diagnostics

  [Network Diagnostics Guide](/run-the-platform/networking/network-diagnostics.md)
* **Node Diagnostics**

  Hardware and system-level troubleshooting

  **Access:** Nodes → \[Select Node] → Diagnostics

  [Node Diagnostics Guide](/run-the-platform/system-administration/node-diagnostics.md)
* **vSAN Diagnostics**

  Storage system analysis and troubleshooting

  **Access:** System → vSAN Diagnostics

  [vSAN Diagnostics Guide](/run-the-platform/storage/vsan-diagnostics.md)
* **NAS Diagnostics**

  Network Attached Storage service troubleshooting

  **Access:** NAS → \[Select NAS Service] → Diagnostics

  [NAS Diagnostics Guide](/run-the-platform/nas/nas-diagnostics.md)

## System-Wide Tools

* **System Diagnostics**

  Comprehensive system-wide diagnostic data collection with direct support integration

  **Access:** System → System Diagnostics

  [System Diagnostics Documentation](/run-the-platform/system-administration/diagnostics.md)
* **Subscriptions & Alerts**

  Proactive monitoring and automated notifications

  **Access:** System → Subscriptions

  [Subscriptions Overview](/run-the-platform/system-administration/subscriptions-overview.md)
* **Prometheus Exporter**

  Integration with external monitoring systems (Grafana, AlertManager)

  **Access:** System → Prometheus Exporter

  [Prometheus Exporter](/automate-protect-and-extend/integrations-and-apis/prometheus-exporter.md)

## Best Practices

**Systematic Approach:**

1. Define the problem scope and timeline
2. Start with targeted component diagnostics
3. Use System Diagnostics for complex issues
4. Document findings and escalate when needed

**Proactive Monitoring:**

* Set up Subscriptions for ongoing health monitoring
* Use Prometheus integration for long-term trend analysis
* Establish performance baselines with diagnostic tools

***

{% hint style="success" %}
**Need Help?**

For complex issues or performance optimization, contact [VergeOS Support](/support-and-services.md) with System Diagnostics data and detailed issue descriptions.
{% endhint %}


---

# 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/run-the-platform/maintenance-and-monitoring/diagnostics-overview.md?ask=<question>&goal=<user_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.