> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/zh/wang-luo/tracking-net-statistics.md).

# 跟踪网络统计信息

为 VergeOS 中的网络规则启用并查看按规则流量统计跟踪，包括防火墙、NAT 和转换规则的包和字节计数器。

统计跟踪可为以下对象启用： *接受、丢弃、拒绝* 和 *翻译* 规则。这允许查看某条规则处理的总数据包/字节数。目前，统计信息无法为以下对象跟踪： *路由* 规则。

## 为网络中的所有非路由规则启用统计跟踪

{% hint style="info" %}
**需要重启网络。**
{% endhint %}

1. 在网络仪表板中，单击 **编辑** 左侧菜单中的。
2. 选中 **跟踪所有规则的统计信息** 复选框。
3. 单击 **提交**.
4. 单击 **重启** 左侧菜单中的该项以重置并应用更改。正常重启会导致短暂中断。

有关查看已跟踪统计信息的说明，请参见下方。

## 为单个规则启用统计跟踪

1. 在网络仪表板中，单击 **规则** 左侧菜单中的。
2. 双击所需规则。
3. 选中 **跟踪规则统计信息** 复选框。
4. 单击 **提交**.
5. 单击 **应用规则** 左侧菜单中的。

有关查看已跟踪统计信息的说明，请参见下方。

## 重置计数器/清除单个规则的统计信息

1. 在网络仪表板中，单击 **规则** 左侧菜单中的。
2. 单击所需规则以进行选择。
3. 确认已选中所需规则（左侧复选框将被勾选）。
4. 单击 **清除统计信息** 左侧菜单中的该项。此规则的数据包/字节计数器将从零重新开始。

## 显示规则统计信息

1. 在网络仪表板中，单击 **规则** 左侧菜单中的。
2. 右键单击顶部的列标题部分。
3. 勾选以下项目的复选框： **数据包** 和/或 **字节** 以显示这些列。

![显示统计信息](https://664309245-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpODKGSQETqL1gSqyxIq3%2Fuploads%2Fgit-blob-f1b7db9e012cc4e8de1d449804bcc2168217fc95%2Ftrackstats-cols.png?alt=media)

{% hint style="success" %}
**启用“统计”列将显示每条规则是否已启用统计跟踪。**
{% endhint %}


---

# 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.verge.io/run-the-platform/zh/wang-luo/tracking-net-statistics.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.