What if I want to monitor something that isn't being monitored?
There are a couple of reasons why LogicMonitor might not be monitoring something for your device:
Case 1: A datasource exists, but Active Discovery isn't enabled
This is the case for most services and processes - Active Discovery is disabled to avoid discovering hundreds of processes and services you aren't interested in monitoring. Instead, it typically makes more sense to manually add the specific processes/services you do want to monitor as instances. You can check the Datasources section of the Settings Tab to view and search all available LogicMonitor datasources (you can also check whether or not Active Discovery is enabled in each datasource definition).
Case 2: A datasource exists, but no instances were discovered
This is typically caused by a configuration issue or a lack of permissions associated with account the collector services are running under. The following table lists the ports that should be open in order for your collector to monitor devices via common protocols:
After making changes to port configuration, permissions, etc. make sure to manually run Active Discovery to see if instances are discovered.
Note that for WMI, port 135 is used to have DCOM dynamically allocate the proper high port which will then make a secondary connection. If one has a server that is behind a non-host or 3rd-party firewall, then port 24158 will be used.
Case 3: A datasource does not exist, but one can likely be created
If you've checked out our datasource library (Settings | Datasources) and we don't have a datasource to monitor what you'd like to see, it is likely that we can monitor it but haven't had a request to do so thus far. LogicMonitor's customizable nature makes it possible to monitor almost anything - if you're comfortable with how LogicMonitor works, you can probably create the datasource yourself. Contact LogicMonitor Support under the ? icon in the top panel of your account if you can't find what you're looking for.