> For the complete documentation index, see [llms.txt](https://www.axisnow.io/zh/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.axisnow.io/zh/docs/edge/insight/dashboard.md).

# 仪表板

控制台首页：全租户的请求、流量、错误率、状态码与事件

控制台首页，统计当前租户全部域的流量；每个数字旁的变化是与上一周期（上小时、上日、上周）的对比。页面不自动刷新。

![](https://3062891322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKDgGNU6JXG7cqYCk2aCz%2Fuploads%2Fgit-blob-c2d97252bd399bf3d6c509a54354ab1e4d15d384%2Fdashboard.png?alt=media)

## 流量卡 <a href="#traffic" id="traffic"></a>

<table data-search="false"><thead><tr><th width="120">卡</th><th>口径</th></tr></thead><tbody><tr><td>请求</td><td>时间范围内到达边缘的请求总数与趋势</td></tr><tr><td>流量</td><td>边缘发往客户端的字节数与趋势</td></tr><tr><td>错误率</td><td>5xx 响应占全部请求的比例。认证、访问控制、速率控制拒绝的 401、403、429 不计入，所以拦截量再大错误率也不变；数值可点击，进入<a href="/zh/docs/edge/insight/log-explorer.md">日志检索</a>并按状态码 ≥ 500 预筛选，达到 10% 时标红</td></tr><tr><td>状态码</td><td>按状态码统计的请求数，列出最多的几个，其余归入「其他」。判断拦截效果看这里：401、403、429 的占比就是各插件拒绝的量</td></tr><tr><td>事件</td><td>时间范围内边缘和平台记录的事件数，按严重、错误、警告、信息分色</td></tr></tbody></table>


---

# 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://www.axisnow.io/zh/docs/edge/insight/dashboard.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.