> 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/policies/access-control/insight.md).
# 洞察与日志
通用访问控制的指标与 IP 封禁记录
规则列表页统计最近 24 小时，用于巡检；洞察页可按时间范围、**Host**、**边缘**、**规则**筛选，用于分析。两处的数字都可点击，进入全局[洞察](/zh/docs/edge/insight/log-explorer.md)的日志检索并带上对应的预筛选。
读数前先明确三个口径：
* **命中**：请求匹配了条件并执行了动作，四种动作都算，跳过也算。
* **挑战**：只统计实际下发了验证页的请求。持有效凭证直接放行的请求计入命中，不计入挑战。
* **IP 封禁**：统计触发次数。封禁期间该 IP 的请求不进入处理，不计入任何指标，也不产生日志。
## 洞察页
* **挑战通过率**：通过 ÷ 发起。未通过包含收到验证页但未作答的请求。
* **封禁中的 IP**：此刻仍在封禁期内的 IP 数，分规则的 IP 封禁动作和挑战的自动封禁两类。
* **命中时间线**：开启了自适应挑战的规则，进入挑战状态的时段会标在图上。反复进入说明阈值接近正常峰值，或攻击在持续。
* **命中来源**：按 **Host** 或**国家**列出前 10 名及动作构成。没有加 Host 条件的规则在这里能看到实际影响了哪些站点。
## IP 封禁记录
时间范围内的每一次封禁，可按**客户端 IP**、**状态**、**规则**筛选。封禁只在触发它的那个边缘生效；同一 IP 在之前 24 小时内被封过会带「24h 内第 N 次」标签。展开一行可看到完整记录，包括封禁发生时的规则配置。记录只读，没有手动解封。速率控制的封禁是同一套机制，各自的洞察页只列自己规则触发的记录。
## 日志
请求明细在全局洞察的日志检索里看，每条日志列出命中的规则和执行的动作。日志经过采样，部分请求查不到，不影响指标。
---
# 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/policies/access-control/insight.md?ask=&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.