---
title: Live Logs
description: Tail the Edge Server\
source: https://documentation.controlcomtech.com/build/edge-server/web-interface/tools/logs
---

# Live Logs

`/tools/logs` is a tail-style view of the Edge Server's structured logs, streamed live as the process produces them.

> **Workflow Stage: Collect**

**Display filters** (client-side, do not change what the server emits)

* **Search**: case-insensitive match against category and message.
* **Min Level**: Trace, Debug, Information, Warning, Error, or Critical.
* **Category pills**: click any category to toggle its visibility; struck-through pills are hidden.

**Service-level overrides** (runtime, server-side)

The collapsible **Override service levels** section lets you raise or lower the minimum log level for a service prefix at runtime, for example to flip `ControlCom.EdgeServer.Modbus` to Trace while you're debugging a polling issue. Pick services, choose a level, and click **Apply**. Active overrides appear as removable chips. These overrides revert on restart, so you cannot accidentally leave the server in a noisy state.

**Stream controls**

* **Pause** / **Resume**: stop or resume ingestion of new entries (independent of filtering).
* **Clear**: empties the local display only; nothing is deleted on the server.

Entries are listed newest first, capped at the most recent 1000. Each entry shows a timestamp, a level pill (TRAC / DEBU / INFO / WARN / ERRO / CRIT), the category, the message, and, on warnings and errors, an expandable stack trace.

> The Live Logs view is the fastest way to confirm what the Edge Server *thinks* is happening. If something looks broken in another page (a client refuses to connect, a command silently no-ops), open Live Logs first, raise the relevant service to Debug, and re-trigger the action.