> 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/administration-and-setup/settings/log-settings.md).

# Log Settings

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-101d32b3d29da5c29047cb7a4f0baf86b26bd02b%2Fprior-t011-en.png?alt=media" alt="Activity-log filters with log entries hidden."><figcaption><p>Activity-log filters with log entries hidden.</p></figcaption></figure>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-d0806b7357356df2114d0360c9a6234ba96f1765%2Fdbdc-855-activity-logs-service-en-20261031.png?alt=media" alt="Activity Logging in the English interface: the log-table headings are Timestamp, Severity, Service and Message. Service identifies the generating service and matches the Service filter above. Log entries and export metadata are outside this view."><figcaption><p>Activity Logging in the English interface: the log-table headings are Timestamp, Severity, Service and Message. Service identifies the generating service and matches the Service filter above. Log entries and export metadata are outside this view.</p></figcaption></figure>

Activity Logging provides a real-time view of system events across all DocBits services. Use it to monitor processing activity, troubleshoot errors, and audit system behavior.

## Analytics Banner

At the top of the page, a banner links to the **Analytics Dashboard** for charts, metrics, and real-time monitoring.

## Filters

| Filter          | Description                                                                                                                   |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Time Range**  | Select a time window (e.g., Today, Last 7 Days, Last 30 Days).                                                                |
| **Severity**    | Toggle severity levels to include or exclude: **Debug**, **Info**, **Warning**, **Error**. Each chip shows the current count. |
| **Service**     | Filter logs by service (e.g., api, auth, api-service).                                                                        |
| **Search logs** | Free-text search across log messages.                                                                                         |

## Log Table

| Column        | Description                                                                  |
| ------------- | ---------------------------------------------------------------------------- |
| **Timestamp** | Date and time the event occurred. Sortable.                                  |
| **Severity**  | Color-coded badge: Info (blue), Warning (yellow), Error (red), Debug (gray). |
| **Service**   | The service that generated the log (e.g., api, auth, ocr, export).           |
| **Message**   | The full log message with event details.                                     |

Results are paginated — use the controls at the bottom to navigate pages.

## Footer Actions

| Action            | Description                                                        |
| ----------------- | ------------------------------------------------------------------ |
| **Auto-refresh**  | Toggle to automatically refresh the log view at regular intervals. |
| **Refresh Now**   | Manually refresh the log data.                                     |
| **Export JSON**   | Export the current filtered logs as a JSON file.                   |
| **Download Logs** | Download the complete log data.                                    |


---

# 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/administration-and-setup/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.