The net_connect probe contains options for identification of the alarms and QoS which allow you to associate the QoS with the Profile Name, Host Name, Robot Address, or IP Address.
At the top of the profile there is also checkbox for "Associate Data and Alarms with hostname" - how does this work in conjunction with the above settings?
DX UIM - Any Version
net_connect probe - 4.01 or higher
These options operate independently of each other.
The dropdown for "QoS Identification Method" influences the "target" field for the QOS_MESSAGE which is sent by the probe.
The dropdown for "QoS Source" influences the "source" field for the QOS_MESSAGE.
Both of these dropdowns affect how the data is recorded in S_QOS_DATA.
The dropdown for "Alarm Identification Method" influences the "Source" field on the ALARM message sent by the probe, which affects the display in the Alarm Console in terms of what the "source" field for the alarm contains.
The checkbox at the top of the profile influences the 'dev_name' which is sent for the device in the discovery data, which ultimately determines which device in Operator Console the QoS and alarms are associated with -- where the charts and alarms appear in relation to the devices.
In most cases, the net_connect profile name and hostname being monitored are the same, so this box does not have an impact - the data ends up associated with the monitored host regardless.
However, it is possible to rename a net_connect profile to something other than the hostname, or to use a "virtual hostname" in the "Host Name" field of the profile, and in such cases, the "Associate Data..." checkbox influences where the data will be displayed.
It is easiest to understand the impact with a series of examples. Refer to the following chart for guidance:
| If the Profile Name Is... | And the Host Name Is | With Associate Data... box checked: | With Associate Data... box not checked: |
| The name of the monitored host | The name of the monitored host | Data will be associated with the monitored host | Data will be associated with the monitored host |
| A virtual hostname | The name of the monitored host | Data will be associated with the monitored host |
Data will be associated with the virtual hostname |
| The name of the monitored host | A virtual hostname | Data will be associated with the virtual host |
Data will be associated with the monitored host |
| The robot where the probe is installed | A second robot | Data will be associated with the second robot |
Data will be associated with the robot where the probe is installed |
| A second robot | The robot where the probe is installed | Data will be associated with the robot where the probe is installed |
Data will be associated with the second robot |