> For the complete documentation index, see [llms.txt](https://docs.spydra.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spydra.app/how-to/private-network/nodes/node-dashboard.md).

# Node Dashboard

The Node Dashboard is designed to provide a visual representation of these metrics, making it easier to understand and analyze the performance of nodes in the network. It enhances the monitoring capabilities of a Network, allowing you to keep track of the health and resource usage of the nodes in real time.

\
The Node Dashboard displays metrics related to the CPU and memory usage of the nodes.

The **CPU graph** represents the utilization of the central processing unit (CPU) over time, showing how much processing power is being used by the node. This graph can help identify periods of high or low CPU usage, which can be useful for performance analysis and capacity planning.

The **memory graph**, on the other hand, represents the memory consumption of the node over time. It shows how much memory is being used by the node's processes and can help identify memory leaks or excessive memory usage that could impact the node's performance or stability.

<figure><img src="/files/lP6rKLsTVL3igkX7LHSP" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.spydra.app/how-to/private-network/nodes/node-dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.