15 Jan 2025 09:09 AM
What is the primary purpose of using a target list in NAM monitoring for hosts or devices that are not known to Dynatrace yet?
Solved! Go to Solution.
15 Jan 2025 09:10 AM
The target list is the only way of configuring NAM monitoring to be used for hosts or devices that are not known to Dynatrace yet, which means no One Agent deployed on hosts and no monitoring with Dynatrace extensions. It is recommended for devices where OA can't be deployed for technical reasons or organization limitations. You need to provide a single IP address/hostname or a list of them divided by commas, for example: 192.168.32.32, 192.168.32.38
The Target filter approach is recommended for configuring the NAM monitoring for devices/hosts that are already known to Dynatrace, such as hosts on which OA is deployed (and configured as a host group) . In such a case, you may define the whole group as your target, and Dynatrace will ping all the interfaces of hosts belonging to the given group (optionally limited to the provided IP address range).
Of course, you may also provide the IP addresses as a list. However, the extra benefit of the approach with the Target filter is that new hosts added to the host group are automatically known for NAM. That means those will be monitored with ping tests without any change in NAM configuration.
Please notice that approaches with a Target list and Target filter might be combined within a single step of NAM monitor. In such a case, the target for NAM testing will be the sum of targets from those two fields. In other words, we do use logical OR between the Target list and the Target filter.