- About LogicMonitor
- Cloud Monitoring
- Dashboards and Widgets
- Resources Page Overview
- Adding & Managing Devices
- Applying Datasources & Instances to Devices
- Device Groups
- Getting Started
- LM Service Insight
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
LogicMonitor has DataSources that enable you to monitor web pages, processes, services and UNC Paths. By default, Active Discovery is disabled for these DataSources. Web Pages and UNC Paths will need to be added as instances on a per-device basis.
If you’d like to monitor a consistent set of processes or services across many devices, it is more efficient to clone an existing DataSource that already monitors processes or services, such as the WinProcessStats- or WinService- DataSource, enable Active Discovery, and add filters to match the processes or services you wish to monitor. (Cloning an existing DataSource for this purpose is documented in detail as a use case in Active Discovery.)
If, on the other hand, you’d like to monitor services or processes on a per-device basis, follow these instructions:
- For each device you’d like to configure web page, process, service or UNC path monitoring for, navigate to the device in the Resources tree, available from the Resources page.
- With the device highlighted in the Resources tree, click the down arrow icon button located next to the Manage button and select “Add Other Monitoring” from the dropdown menu that appears.
The name of the monitored web page as it will appear in LogicMonitor.
The full URL for the web page, or the relative URL path for the web page if the website domain is already associated with the device.
The HTTP per Page DataSource will load the web page, and provide a status and the page load time:
Processes and Services
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.
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.
After you have selected “Add Other Monitoring,” a new window will open. Here, you should add the relevant Processes/Services. Note that the “Type” field (Windows or Linux) will auto-populate based on the device to which you’re adding the Proccess or Service.
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 WinProcessesStats DataSource and Windows services will be monitored by the WinServices DataSource.
To monitor a UNC share, whether a domain DFS share or otherwise, use the UNC Monitor DataSource. This DataSource will do a directory listing on the given UNC share and report success or failure.
To add a share to be monitored, select a Windows host in the hosts view. The monitoring of the UNC actually occurs on the collector that monitors this host, but the results can be associated with any windows host.
For Windows devices, the additional option to monitor UNC Paths will appear in the Additional Monitoring dialog:
The name of the monitored UNC path as it will appear in LogicMonitor.
The UNC path. This can be a path to a directory or a specific file (e.g. \\fs\root\builds)
LFS paths (C:\Windows) are also supported.
The UNC Monitor DataSource will monitor the accessibility of the UNC path from the collector monitoring this device.
In this Article: