---
title: "How to Create Monitor Logs with Log4net On-Premises ONLY"
slug: "how-to-create-monitor-logs-with-log4net-on-premises-only"
updated: 2025-11-09T13:34:20Z
published: 2025-11-09T13:34:20Z
canonical: "support.controlup.com/how-to-create-monitor-logs-with-log4net-on-premises-only"
---

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

# How to Create Monitor Logs with Log4net On-Premises ONLY

To troubleshoot effectively, our technical teams might need a detailed log of the ControlUp Monitor. We use **[log4net](https://logging.apache.org/log4net/)** as a third-party logger to allow you to log the activity of the monitor in different log levels.

For ControlUp for VDI versions pre 9.0 and on-premises versions, the monitor machines don't automatically create log files, so you still need to [manually create](/v1/docs/how-to-create-monitor-logs-with-log4net#create-the-log-file-manually-pre-90) a log file.

## Create Log File Manually (pre 9.0)

1. On your monitor machine, navigate to the ControlUp Monitor folder **C:\Program Files\Smart-X\ControlUpMonitor\Version 8.x.x.xxx**
2. Download and copy the file **[cuMonitor.exe.log4net](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/cuMonitor.exe.log4net)** to the monitor directory.
3. Right-click the monitor folder > **Security**. Add the NETWORK SERVICE user.  

![NETWORK SERVICE user added](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-4U8I86RQ.png)
4. Assign **Full control** permission to the **NETWORK SERVICE** user.  

![full control permission assigned to NETWORK SERVICE user](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-1U7BRBSZ.png)
5. You can now see a new file **ControlUp.log**.  

![ControlUp.log file](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-KUS2R2Q1.png)  

If you want to change the file name you can edit the following value in the cuMonitor.exe.log4net file:

```
<file value="ControlUp.log"/>
```

## Settings in Log4net File

### Set the Log Level

You can set the [log level](https://logging.apache.org/log4net/log4net-1.2.13/release/sdk/log4net.Core.Level.html) (e.g., DEBUG, ERROR, WARN) by changing the following value.

```
<root>
<level value="DEBUG"/>
<appender-ref ref="RollingFileAppender"/>
</root>
```

          Information

          

The debug level is a lower log level than the info level. This means that log statements written at the debug level are generally considered to be less important or severe than log statements written at the info level

### Set the Maximum File Size

To change the file size, modify the value in the **[maximumFileSize](https://logging.apache.org/log4net/log4net-1.2.12/release/sdk/log4net.Appender.RollingFileAppender.MaximumFileSize.html)** key.

```
<maximumFileSize value="50MB"/>
```

### Set Rollback Policy

Define how many files are written after the maximum file size has been reached. You can find more information [here](https://logging.apache.org/log4net/log4net-1.2.12/release/sdk/log4net.Appender.RollingFileAppender.MaxSizeRollBackups.html).

```
<maxSizeRollBackups value="5"/>
```