---
title: "Custom Hive Logs and Debugging"
slug: "debugging-logs"
tags: ["Synthetic Monitoring"]
updated: 2025-07-17T16:03:44Z
published: 2025-07-17T16:03:44Z
canonical: "support.controlup.com/debugging-logs"
---

> ## 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.

# Debugging Logs

Custom Hive debugging logs can help identify the cause of issues with your Scouts. If you are creating a support request with ControlUp Support, then you should send the debugging logs for the Scout that is not working correctly. 

This article describes how to get the debugging logs for a Scout running from a Custom Hive.

## Step 1 - Enable Debug Mode on Your Custom Hive
Debugging logs are stored only if debug mode is enabled on the Custom Hive.

To enable debug mode:
1. On the machine where the Custom Hive is installed, open the Custom Hive configuration in `C:\Program Files\Scoutbees Custom Hive\sb-config.exe.
![Hive installation folder](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/Hive%20installation%20folder.png){height="" width=""}

2. Go to the **Advanced** tab and make sure that **Debug Mode** is enabled.<p><img 
![Allow Debug mode in configuration screen](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/Allow%20Debug%20modee%20in%20configuration%20screen.png){height="" width=""}

3. Click **Save**.

## Step 2 - Get the ID of your Scout
To get the debugging logs for a specific Scout, you need to know the Scout ID.

To find the Scout ID:
1. In Synthetic Monitoring, select the Scout to go to the Scout details page.

![Select scout details](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/Select%20scout%20details.png){height="" width=""}

2. In your browser URL, a number appears after the name of the Scout. This is the ID of the Scout.

![Scout ID](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/Scout%20ID.png){height="300" width=""}

## Step 3 - Get the Debugging Logs for the Scout
Now you can get your debugging logs for the Scout. Logs are stored with the Custom Hive that runs the Scout.

1. On the machine where the Custom Hive is installed, go to `C:\Program Files\Scoutbees Custom Hive\logs`.
2. Look for a file called `runner-xxxxx-...` where xxxxx is the ID of the Scout that you found in step 2. This is the debugging log for the Scout. A separate log is created each time the Scout runs.<p><img src="https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/DebugLog.png" style="box-shadow: 0 0 23px rgba(0,0,0,.1)"></p>

## Debug Mode in Custom Hives during Upgrade
### Debug Installation
Note that you can run a Debug mode installation when upgrading a hive. Here is an example for a debug mode script:

![Script for Debug install in Vanilla](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/Script%20for%20Debug%20install%20in%20Vanilla.PNG){height="" width=""}

There are two ways to perform debug mode installation:

1. With the **previous parameters**, including *debug_mode*. For instance:
![debug mode with parameters](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/debug%20mode%20with%20parameters%281%29.PNG){height="" width=""}

2. Debug installation of a hive that includes **change of parameters** - *Revert All but Debug*:
![debug mode that includes change of parameters](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/debug%20mode%20that%20includes%20change%20of%20parameters.PNG){height="" width=""}

To return to the **default parameters**, use the following script. This script does not include the Debug parameter:
![Return to default](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/Return%20to%20default.PNG){height="" width=""}