---
title: "Rocket Chat Workspace Log Configuration"
slug: "configure-workspace-logs"
description: "Learn how to configure workspace logs in Rocket Chat. Ensure secure tracking, auditing, and compliance."
updated: 2026-05-18T20:42:24Z
published: 2026-05-18T23:04:08Z
canonical: "docs.rocket.chat/configure-workspace-logs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Workspace Logs

Logs provide detailed insight into workspace activity and help diagnose failures or errors. Workspace administrators can control which logs and metrics Rocket.Chat should release. This guide explains how to configure the available settings.

> [!WARNING]
> Server logs access viewer was removed in Rocket.Chat 8.0
> 
> We recommend configuring an observability stack. For more details on how to view your workspace logs and metrics, refer to the [Monitor Workspace Logs and Metrics guide](/v1/docs/access-workspace-logs).

## Configure logs

To access this page, go to **Manage** ![Screenshot 2025-12-23 130522.png](https://cdn.us.document360.io/6ae79a05-7252-45d0-96e8-8f375e07b1b2/Images/Documentation/Screenshot%202025-12-23%20130522.png) > **Workspace** > **Settings** > **Logs**. Modify the following settings:

| Field | Description |
| --- | --- |
| **Log Level** | From the drop-down menu, select the level of logs to receive. The options are: - **0 - Errors Only**: Displays the errors only. - **1 - Errors and Information**: Displays various workspace activities and errors. - **2 - Errors, Information, and Debug**: Displays debugging details. Use this option for detailed log entries. |
| **Trace method calls** | Enable this option to trace every method call. |
| **Trace method filter** | Enter specific text to filter the traced method calls. The text here is evaluated as a regular expression (`new RegExp('text')`). Keep it empty to show a trace of every call. |
| **Trace subscription calls** | Enable this option to trace every subscription call. |
| **Trace subscription filter** | Enter specific text to filter the traced subscription calls. The text here is evaluated as a regular expression (`new RegExp('text')`). Keep it empty to show a trace of every call. |
| **Log Exceptions to Channel** | Enter the name of an existing channel to receive all captured exceptions. Leave empty to ignore exceptions. |

## Configure Prometheus

If you have set up a Prometheus server for monitoring purposes, you can integrate it with Rocket.Chat. On the workspace’s **Logs** page, update the following **Prometheus** settings:

| Field | Description |
| --- | --- |
| **Enable** | Enable this option to activate Prometheus monitoring. |
| **Port** | The port to listen to. |
| **Reset Interval (ms)** | Enter the time (in milliseconds) when the connection should be reset. |
| **Collect NodeJS GC** | Keep this option enabled always to activate NodeJS garbage collector. It’s useful for debugging. |
| **API: Track User Agent** | Enable this option to track the API calls of user agent. |

> [!WARNING]
> If you enabled monitoring when [deploying your Rocket.Chat workspace](/v1/docs/deploy-rocketchat), the Prometheus settings were configured automatically. Do not modify them, as this may disrupt monitoring.

---

## Configure troubleshooting

Configure how troubleshooting is handled in your workspace.

To access this section, go to **Manage** ![Screenshot 2025-12-23 130522.png](https://cdn.us.document360.io/6ae79a05-7252-45d0-96e8-8f375e07b1b2/Images/Documentation/Screenshot%202025-12-23%20130522.png) > **Workspace** > **Settings** > **Troubleshoot**.

> [!CAUTION]
> We recommend these settings be altered only with the guidance of the Rocket.Chat Development or Support Teams. Do not make any changes without assistance or you may encounter disruptions in the workspace functionality.

| Field | Description |
| --- | --- |
| **Disable Notifications** | Enabling this setting disables the notifications system completely. Sounds, desktop, mobile, and email notifications immediately stopped. |
| **Presence broadcast disabled internally** | This indicates whether the presence broadcast is disabled automatically. This can occur in workspaces with no [premium](/v1/docs/our-plans) license and over 200 concurrent users. |
| **Disable Presence Broadcast** | Enable this setting to prevents all instances from sending the users' status changes to their clients, keeping all users with their presence status from the first load. |
| **Disable Instance Broadcast** | Enabling this option prevents the Rocket.Chat instances from sending events to the other instances. It may cause syncing problems and unexpected behavior. |
| **Disable Sessions Monitor** | Enabling this setting stops the processing of user sessions, causing the statistics to stop working correctly. |
| **Disable Livechat Activity Monitor** | Enabling this setting stops the processing of Livechat contacts sessions, causing the statistics to stop working correctly. |
| **Disable Data Exporter Processor** | Enabling this setting stops the processing of all export requests from users, so they will not receive the link to download their data. |
| **Disable Teams mention** | Enabling this setting disables the teams mention feature, preventing users from mentioning a team by name in a message. |
| **Force browsers to clear networking cache based on version change** | Enabling this setting allows browsers to clear the cache based on the provided version. If the value provided is not empty and different from previous one, the browsers will try to clear the cache. This setting should not be set for a long period of time since it affects the browser performance, clear it as soon as possible. |