ResolutionPlease go to Administration │ Agents │ Agent Status │
Choose the Windows Agent that is being affected and click on Edit │ Edit Properties │ Modify the private properties for this agent.
A.
1. If there are two different host objects referring to the same host, one is "servername", the other is its FQDN. Then please set "Collect System ID" to "True" to see whether the two host objects can be merged.
Note: Trying to change the host name override value but changing the actual host value wouldn't help.
2. Please go to Administration │ Credential │ Manage Credential
Choose the credential where that host is defined and click on Edit, then "Resource Mappings"
Please do the following adjustments which will re-enable the monitoring of "Servername.com" host, where you have:
Usage equals 'Infrastructure Monitoring for Windows' AND Target Host Name is domain name 'Servername'
Change it to:
Usage equals 'Infrastructure Monitoring for Windows' AND Target Host Name is domain name 'Servername' or 'Servername.com'
Then deactivate and activate the agent again from Agent Status.
B
About the Servername in question, please try below steps and check the issue again.
1. In Navigation Panel │ Administration │ Tooling │ Script Console, copy and paste below query in the field "Do Query", then click "Do Query", please check how many rows you can get.
!Host where name like 'SERVERNAME%' or name like 'servername%'
2. Please navigate to Navigation Panel │ Administration │ Management Server │ Servers │ Object Cleanup │ Object Management, in the dashboard "Investigate Objects for Cleanup" click "Host Model" -> hosts, then check how many host objects you can see regarding to "servername" or "SERVERNAME"
3. If you can see 2 rows in item #1 and 2 objects in item #2, you can jump to below items.
4. Stop the FglAM that is collecting metrics for that object.
5. In the dashboard "Investigate Objects for Cleanup" you can select the one host objects with less(or empty) topology/observations, then click "Delete" to remove this host object.
6. Start the FglAM that is collecting metrics for that object, then check the issue again.
Another scenario where Inferred may be seeing after configured SQL Server cluster (which is a logical configuration) with it's two notes: ServerX and ServerY, those last two are being monitored also by Infrastructure agent, each one has it's own agent.
But the SQL Server Cluster which does not have an Infrastructure agent created appears under "Inferred" tile under Infrastructure dashboard.
Solution:
1. The logical host name cannot be removed, the DB cartridge uses it for the alarm.
2. The DB cartridge do not have a preferred setting for these properties and during the installation of an Infrastructure agent it keeps them with the default settings.