> 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.md).

# 洞察

仪表板、插件与端点洞察、日志检索各看什么

指标回答流量和拦截有多少，日志回答某个请求发生了什么。两者都不是实时的，按日志处理进度有约一分钟的延迟；指标页上的数字大多可以点击，进入[日志检索](/zh/docs/edge/insight/log-explorer.md)并带上对应的筛选条件。

## 从哪里看 <a href="#where" id="where"></a>

<table data-search="false"><thead><tr><th width="160">位置</th><th>回答的问题</th><th width="260">页面</th></tr></thead><tbody><tr><td>仪表板</td><td>全部域的请求、流量、错误率和状态码分布</td><td><a href="/zh/docs/edge/insight/dashboard.md">仪表板</a></td></tr><tr><td>插件洞察</td><td>每条规则最近 24 小时的命中趋势；通用访问控制、速率控制、缓存控制有各自的洞察页，看动作、来源和封禁记录</td><td><a href="/zh/docs/edge/policies/access-control/insight.md">通用访问控制</a>、<a href="/zh/docs/edge/policies/rate-limiting/insight.md">速率控制</a>、<a href="/zh/docs/edge/policies/cache/insight.md">缓存控制</a></td></tr><tr><td>端点与源站</td><td>域列表的 24 小时访问次数与错误率；源地址的回源错误率、重试、源站性能和健康检查事件</td><td><a href="/zh/docs/edge/endpoints/origin-address/insight.md">源地址 › 洞察与日志</a></td></tr><tr><td>日志检索</td><td>按条件查请求明细，展开看链路拓扑、耗时瀑布和全部字段</td><td><a href="/zh/docs/edge/insight/log-explorer.md">日志检索</a>、<a href="/zh/docs/edge/insight/log-fields.md">日志字段</a></td></tr></tbody></table>

要把原始日志送进自己的系统，用[日志推送](/zh/docs/edge/integration/log-receiver.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://www.axisnow.io/zh/docs/edge/insight.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.