> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/frequently-asked-questions/grafana-ui-does-not-load-metrics-for-kubernetes-dashboard-for.md).

# Grafana UI Does not Load Metrics for 'Kubernetes' Dashboard for Clusters with Large Node Count

## Problem

* Grafana visualization is impacted for a specific dashboard - *Kubernetes.*
* *Kubernetes* dashboard is working when a subset of nodes are selected but is not able to display data for all the nodes at once.
* The error showing up on UI is - `Unknown error during query transaction. Please check JS console logs.`

## Environment

* Platform9 Managed Kubernetes - v5.6.8 and Higher

## Answer

* Platform9 is aware of this issue and an internal bug for the same has been reported with the ID: **PMK-6323**

## Additional Information

* This issue is likely to occur with Kubernetes clusters having node count of greater than 200.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/frequently-asked-questions/grafana-ui-does-not-load-metrics-for-kubernetes-dashboard-for.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 `build a script that syncs our docs to a CMS` 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.