Skip to main content

4. Detecting and monitoring new systems with Discovery

Pandora FMS Discovery tool provides a set of tools to simplify monitoring through wizards, including Discovery's Network Scan feature.

To use it, follow these steps. In the side menu, go to DiscoveryHost&Devices → Network Scan section.

pfms-management-discovery-host_and_devices-netscan.png

Create the task as follows: Modify only the network range to be scanned, in this screenshot it is 192.168.70.0/24, which means that all hosts on network 192.168.70.xx will be scanned. Select the "Unknown" group, which will be used to contain the devices you detect in that group. From now on, the devices managed and/or monitored by Pandora FMS will be called "agents".

image-1603908502282.png

You may select different aspects of the initial monitoring that will be applied to the discovered devices. You may define different pre-configured templates, as you may see in the image. Choose the option "BASIC MONITORING" and leave the option "Review results" unchecked.

image-1603908571508.png

Once the recognition task is created, as it was created with manual interval, start it manually. For that, force its execution in the discovery task list:

ab3-3.png

Its progress will be updated:

image-1603909280645.png

At any time, you may click on the magnifying glass icon to see the task details:

image-1603908709046.png 

image-1603909343615.png

At this point, it is better to wait until the whole network is scanned. When it is finished, go to the agent detail view to see all the detected systems. Menu "Monitoring" > "Views" > "Agent detail", as seen in the image:

ab3-7.png

 

You will see several systems that were detected. In some cases, the name of the system will have been solved (if it was possible by DNS) and in others, the type of Operating System will have been detected, according to the options selected in the network scan carried out with Discovery. Clicking on the name will lead you to the agent detail view, which will show all the system information. In this case, the agent has only one module, the "Host alive" module, a check that verifies whether the machine is "alive" and responds from the network, and the "Host Latency" module, which calculates the time it takes for the server to communicate with the machine:

ab3-8.png

If you do not need more monitoring or configuration, go to the metric alert here.


Did you not get the expected results? Go to help or support sections.