> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/dashboard/troubleshooting.md).

# 故障排除

## 以下是解决与仪表板设置相关的常见问题的具体提示：

**筛选器未正确应用：**

* 首先，检查筛选器设置，确保已应用正确的筛选器，并且显示的是所需数据。
* 确保筛选器的应用逻辑正确且一致。有时，错误的筛选逻辑或筛选器组合可能会导致意外结果。
* 为用户提供正确使用筛选器的指导，确保他们能够有效使用筛选功能。

**数据加载延迟：**

* 检查网络连接，确保连接稳定且不会造成延迟。
* 检查服务器负载和数据源性能，确认问题是否出在这两处。可能需要优化数据源，或切换到性能更强的基础设施。
* 实施缓存机制以缩短加载时间，尤其是对于频繁访问的数据。鼓励用户优化数据查询，只获取所需的数据字段，并使用筛选器减少数据量。

**浏览器问题：**

* 确保用户使用的浏览器与仪表板兼容，并已安装所有必需的更新。
* 建议用户定期清除浏览器缓存，以避免内存问题，并确保获取最新数据。
* 检查浏览器中是否有可能干扰仪表板的扩展或插件；如有必要，暂时将其禁用以排查问题。

**特定用户问题：**

* 为仍然遇到问题的用户提供个性化支持。可能需要检查其具体设置、权限或网络配置，以找出并解决问题。

提供这些具体的故障排除提示，有助于用户有效解决与仪表板设置相关的常见问题，并提高工作效率。


---

# 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.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/dashboard/troubleshooting.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.