Adding Additional Monitoring
Last updated - 21 July, 2026
LogicMonitor has DataSources to monitor web pages, processes, services, and UNC Paths. Because Active Discovery is disabled for these DataSources by default, you need to add these as instances for each resource.
- In LogicMonitor, navigate to Resources page, and select the resource.
- In the overflow menu, select Add Additional Monitoring.
- Edit the necessary configurations for each web page, process, service, or UNC path you are adding as a monitored instance.
These configurations are detailed in the following sections:
Web Pages
- Name – The name of the monitored web pages as it will appear in LogicMonitor.
- URL/Path – The full URL for the web page, or the relative URL path for the web page if the website is already associated with the device.
Processes and Services
- Type – The type of process or service you are adding. The dropdown values for this field will be limited based on whether the device runs a windows or Linux Operating System.
- Processes/Services – The process or service to be monitored. The dropdown values for this field will be pre-populated based on the processes and services running on your device.
- Description – The description for the monitored process or service, as it will appear in LogicMonitor.
Linux processes will be monitored by the LinuxNewProcesses DataSource, Windows processes will be monitored by the WinProcessStats DataSource and Windows services will be monitored by the Microsoft_Windows_Services DataSource. For more information about monitoring Linux services, see Linux SSH Monitoring.
UNC Path Monitoring
You can configure UNC path monitoring for any Windows resource. Although the monitoring actually occurs on the Collector that monitors this resource, the results can be associated with any Windows resource.
| Field | Description |
|---|---|
| Name | Enter the name of the UNC path as it displays in LogicMonitor. |
| URL/Path | Enter the UNC path to monitor. You can specify a directory or file (for example, \\fs\root\builds). Local file system paths are also supported (for example, C:\Windows). |
Note: The hostname used in the path/URL field must match the system.hostname property of the device. If not, the following error displays:
“Unknown device, Due to security reasons, monitoring is only supported on already discovered/added devices”.
Supported Path Formats
You can specify one of the following path formats:
| Path Type | Format | Notes |
|---|---|---|
| Network UNC | \\<server>\<share>[\<folder>...]For example: \\fs\root\buildsAlso supported: //<server>/<share>[/<folder>...]For example: //fs/root/builds | The server name or IP address must match a resource already added to LogicMonitor. Use the same hostname or IP format configured for the resource (for example, short hostname or fully qualified domain name). |
| Local path | C:\<folder>...For example: C:\Windows | No separate file server resource is required. |
Network UNC paths must include both a server name and share name (for example, \\fs\share). Blank or malformed paths are rejected.
Note: LogicMonitor supports both the standard UNC prefix (\\) and the forward-slash format (//) for network UNC paths. For example, both \\fs\share and //fs/share are valid.
The UNC Monitor DataSource verifies that the Collector can access the configured path, enumerate the directory, and report whether the operation succeeds or fails.
To monitor a UNC path, ensure that the account used to access the share has the required permissions. By default, LogicMonitor uses the account specified by the wmi.user property. To use a different Windows account, configure the following properties:
| Property | Description |
|---|---|
win.user | Windows user name. |
win.pass | Windows user password. |
Configure the win.user and win.pass properties from Manage Device > Add Property.
For more information, see Resource and Instance Properties.
