# Configure Log Level

Cloud Voice lets you decide how much detail its system logs capture. By enabling only the log categories that matter to you, you keep the logs focused and easier to work through when you need to troubleshoot. Turning off categories you do not need also keeps log files smaller and quicker to read.

:::note
System logs are recorded on the PBX itself and are separate from call recordings or Call Detail Records (CDR, the summary record of each call). The log level only controls which categories the system writes; it does not delete logs that were already saved.
:::

## Set the log level

1. Sign in to the PBX web portal and open **Maintenance > System Logs**.
2. Select **Log Level**.
3. In the dialog that appears, turn on each category you want the system to track:
   - **Information**: Basic operational details.
   - **Notice**: Notice-level messages.
   - **Warning**: Warning messages.
   - **Error**: Error messages.
   - **DTMF**: Dual-Tone Multi-Frequency signaling, the tones a phone sends when a caller presses a key (for example, choosing an option in an auto attendant menu).
   - **Time Log**: Timestamps applied to system log entries, so you can see exactly when each event happened.
   - **Debug**: Diagnostic detail for CDR handling (for example, CDR data cleansing), plus verbose debug output for these services:
     - **SIP** (Session Initiation Protocol): the signaling that sets up, manages, and ends calls.
     - **RTP** (Real-time Transport Protocol): the stream that carries the actual call audio.
     - **OpenAPI event notification messages**: the events the PBX pushes to integrated third-party applications through its OpenAPI interface.
   - **CDR Log**: Call Detail Record data, the per-call summary (who called whom, when, and for how long).
4. Select **Save**, then **Apply**.

:::tip
For everyday operation, leave **Information**, **Notice**, **Warning**, and **Error** enabled. That set gives you enough history to spot problems without flooding the logs. Enable **DTMF**, **SIP**, **RTP**, or **Debug** only while you are actively chasing a specific issue.
:::

:::caution
**Debug** logging is very detailed and grows log files quickly, which uses more storage and can add load to a busy system. Turn it back off once you have captured what you need, then click **Save** and **Apply** again.
:::

:::caution
Your changes do not take effect until you click **Apply**. Clicking **Save** alone stores the setting but does not activate it, so it is easy to walk away thinking the new log level is running when it is not.
:::

## Result

Each day, the system produces logs for the categories you enabled.