Update Hardware Check Timeout and Concurrent Hardware Check Count

In certain distributed network topologies, you may find that camera snapshots are not coming through in the camera report.  This may be due to increased latency across the network.  In this case, you can adjust the snapshot timeout for both the Boring Toolbox reports as well as the reports run through the web app and scheduled reports. 

To improve report generation performance, update the Milestone Proxy configuration to increase the hardware check timeout and, if necessary, the number of concurrent hardware checks.
 

Option 1: Use the existing configuration file

If the following file exists, open it:

C:\ProgramData\The Boring Lab\Milestone Proxy\appsettings.json

Option 2: Create a new configuration file

If appsettings.json does not exist in the location above:

1. Create a new file named appsettings.json in:
   C:\ProgramData\The Boring Lab\Milestone Proxy\
2. Add the following configuration:

{
  "HardwareCommand": {
    "MaxConcurrentHardwareCheckCount": 10,
    "HardwareCheckTimeout": "00:00:30"
  }
}

If the file already exists

Locate the HardwareCommand section and update the following settings:

Example:

"HardwareCommand": {
  "MaxConcurrentHardwareCheckCount": 10,
  "HardwareCheckTimeout": "00:00:30"
}

Updating MaxConcurrentHardwareCheckCount

If instructed by The Boring Lab Support team, increase the value of:

"MaxConcurrentHardwareCheckCount": 10

For example, to allow up to 20 concurrent hardware checks:

"MaxConcurrentHardwareCheckCount": 20

Note: Increasing this value can improve performance in environments with many cameras but may also increase CPU and network utilization. Only increase it as recommended by support.

Save the file

Save and close appsettings.json.

Note: Because the configuration file is stored under C:\ProgramData\The Boring Lab\Milestone Proxy, administrator privileges are not required.

Verify the change

1. Open Boring Web.
2. Generate the report again with Camera Retention and Snapshots enabled.
3. Confirm the report completes successfully.