---
title: "Enable detailed logging | Lansweeper Platform"
slug: "enable-detailed-logging"
description: "Temporarily raise Network Discovery logging to Debug or Verbose, globally or for a single target, so Lansweeper Support can diagnose an issue faster."
status: "update"
updated: 2026-08-18T10:15:33Z
published: 2026-08-18T10:15:33Z
canonical: "docs.lansweeper.com/enable-detailed-logging"
---

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

# Enable detailed logging

Detailed logging temporarily raises the logging verbosity in Network Discovery so Lansweeper Support can diagnose an issue. You can raise verbosity everywhere at once, or for a single scan target when only one device misbehaves.

Both options are available in the Network Discovery hub in **Settings** > **Troubleshooting**, on the **Detailed logs** and **Target detailed logs** cards.

![The Settings Troubleshooting tab in the Network Discovery hub, showing the Detailed logs card with an Enable toggle, the Target detailed logs card with Target and Detail level fields and an Enable toggle, and the Gather logs card with a Download logs button.](https://cdn.document360.io/21d5935c-1b73-44fa-bf5a-a8b0f5c67f25/Images/Documentation/network-discovery-troubleshoot.png)

## How detailed logging behaves

Both cards work the same way:

- **Immediate effect.** The change applies right away, with no service restart and no editing of `appsettings.json`.
- **Automatic revert.** Logging returns to its original level after 24 hours, or immediately when you turn it off.
- **Held in memory on the hub.** If the hub service restarts, detailed logging is off again and has to be re-enabled.
- **Log files only.** Debug and Verbose entries go to the log files, not the Windows Event Viewer.
- **Recorded in the log.** Both enabling and disabling are written to the log, so the log shows the window during which detailed logging was active.

              Detailed logs grow your log files faster

              

Detailed logging increases the size of your log files quickly. The 24 hour automatic revert limits that growth. Turn logging off as soon as you've captured the issue.

## Enable detailed logging globally

Use the **Detailed logs** card to raise verbosity across the hub, all sensors, and the Update component at once.

1. In the Network Discovery hub, go to **Settings** > **Troubleshooting**.
2. On the **Detailed logs** card, turn on the **Enable** toggle.

Verbosity goes to Debug for every component. This card has no level choice. To capture Verbose logs, use **Target detailed logs** for the specific device instead.

## Enable detailed logging for a single target

Use the **Target detailed logs** card to raise verbosity for one scan target only. This keeps the extra log volume bounded when a single device is the problem.

1. In the Network Discovery hub, go to **Settings** > **Troubleshooting**.
2. On the **Target detailed logs** card, enter the **Target**. Use exactly one IP address or hostname. IP ranges aren't accepted.
3. Select a **Detail level**:
  - **Detailed** raises the target to Debug verbosity.
  - **Very detailed** raises the target to Verbose verbosity, the most detailed level.
4. Turn on the **Enable** toggle to start logging for that target.

Only logs for that target become more verbose. Every other target keeps its original level.

### Detailed and Very detailed

The two detail levels control how much the logs capture:

- **Detailed** logs at Debug level. Debug adds diagnostic messages about what each component is doing, which is enough to investigate most issues.
- **Very detailed** logs at Verbose level, the most detailed setting. Verbose captures the most granular internal activity on top of Debug, and grows the log files the fastest. Use it only when Lansweeper Support asks for it.

## Choose global or single target

The two cards sit side by side. The difference is scope and detail level:

- **Detailed logs** covers everything (hub, all sensors, and the Update component), at Debug level only.
- **Target detailed logs** covers one IP or hostname, and adds a Verbose option for even more detail.

Start with **Target detailed logs** when you already know which device is affected. Use **Detailed logs** when the issue isn't tied to a single target.

## Detailed logging or gather logs?

Detailed logging and gather logs solve different halves of the same problem. Detailed logging controls how much detail the logs capture. [Gather logs for support](/docs/gather-logs-for-support) collects those logs and sends them to Support.

Use them together when the default logs don't show enough to diagnose an issue:

1. Enable detailed logging.
2. Reproduce the issue, so the extra detail is written to the logs.
3. Gather the logs and send them to Support.
4. Turn detailed logging off.

If the default logs already contain what Support needs, gather the logs without enabling detailed logging first.

## Related articles

- [Gather logs for support](/docs/gather-logs-for-support). Collect the hub and sensor logs and send them to Support.
- [Check device connectivity](/docs/check-device-connectivity). Test what a sensor can reach on a single device.
- [Default installation and log file locations for Network Discovery](/docs/discovery-hub-and-sensor-installation-files). Find the hub and sensor install paths and log file locations.