> 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/cache/insight.md).
# 洞察与日志
缓存控制的指标口径与清理预热的任务记录
缓存控制、缓存清理、缓存预热各有一个洞察页。
## 缓存控制
可按时间范围和域名筛选。
* **缓存命中请求 / 缓存命中流量**：`X-Cache` 为命中的请求数和这些响应的出向流量。
* **请求缓存命中率**：命中请求数除以筛选范围内的全部请求数，分母包含动态接口和没有命中任何规则的请求，所以动态内容多的站点天然偏低。
* **请求 / 流量**：总量与命中量的趋势。
* **请求缓存状态 / 流量缓存状态**：按 `X-Cache` 的值分别统计，含义见[工作原理](/zh/docs/edge/policies/cache/how-it-works.md#cache-status)。
两个口径分开看：请求命中率反映源站的请求压力，流量命中率反映带宽节省；`REVALIDATED` 在流量上几乎不回源，在请求数上仍算一次回源。按状态分布调整规则：`REVALIDATED` 多说明缓存时长偏短；`EXPIRED` 多说明源站没有返回 `Last-Modified` 或 `ETag`；`MISS` 多先对比 `X-Cache-Key` 看是否 Key 过细，再看是否节点多、流量分散；`BYPASS` 多先查绕过规则的范围。
单个请求的缓存状态直接看响应头 `X-Cache`，见[工作原理](/zh/docs/edge/policies/cache/how-it-works.md#cache-status)。
## 清理与预热
两个洞察页列出每次提交的任务及其成功、失败条数，展开可看逐条明细；预热的明细可按边缘筛选，能定位到某个节点上某条 URL 的失败原因。
---
# 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/cache/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.
