> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/log-settings.md).

# 活动日志

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-98fb206c2f8d0c58df6db354d9f2f9ae815c9adf%2Factivity_logging.png?alt=media" alt="活动日志"><figcaption><p>活动日志页面</p></figcaption></figure>

活动日志可实时查看所有 DocBits 服务中的系统事件。您可以使用它监控处理活动、排查错误并审计系统行为。

## 分析横幅

页面顶部的横幅链接到 **Analytics Dashboard（分析仪表板）**，可查看图表、指标并进行实时监控。

## 筛选器

| 筛选器      | 描述                                                                                  |
| -------- | ----------------------------------------------------------------------------------- |
| **时间范围** | 选择时间段（例如：今天、最近 7 天、最近 30 天）。                                                        |
| **严重级别** | 切换要包含或排除的严重级别：**Debug（调试）**、**Info（信息）**、**Warning（警告）**、**Error（错误）**。每个标签会显示当前计数。 |
| **服务**   | 按服务筛选日志（例如：api、auth、api-service）。                                                   |
| **搜索日志** | 在日志消息中进行自由文本搜索。                                                                     |

## 日志表格

| 列        | 描述                                                 |
| -------- | -------------------------------------------------- |
| **时间戳**  | 事件发生的日期和时间。可排序。                                    |
| **严重级别** | 按颜色标记的徽标：Info（蓝色）、Warning（黄色）、Error（红色）、Debug（灰色）。 |
| **组件**   | 生成日志的服务或模块（例如：api、auth、api-service）。               |
| **消息**   | 包含事件详情的完整日志消息。                                     |

结果采用分页显示——使用底部的控件浏览各页。

## 页脚操作

| 操作          | 描述                    |
| ----------- | --------------------- |
| **自动刷新**    | 切换是否按固定间隔自动刷新日志视图。    |
| **立即刷新**    | 手动刷新日志数据。             |
| **导出 JSON** | 将当前筛选后的日志导出为 JSON 文件。 |
| **下载日志**    | 下载完整日志数据。             |


---

# 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.docbits.com/chinese/guan-li-yu-she-zhi/settings/log-settings.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.