Which hostname does the SQL Server database agent use for OS collections? (4232449)

The SQL Server database agent determines which hostname to use for OS collections based on agent configuration properties. Recent enhancements introduce the monHostUserNsLookup flag, which changes hostname resolution behavior to prioritize FQDN via DNS lookup.

Prior to the 7.3.0.10 SQL Server cartridge, hostname selection depended on the osUsePhysicalHostName property:

• If osUsePhysicalHostName=1, the agent used the short hostname from SQL Server (ServerProperty('ComputerNamePhysicalNetBIOS')).
• If osUsePhysicalHostName=0, the agent used monHost (which could be FQDN or short hostname).

With the addition of monHostUserNsLookup and the installer agent flag, the agent can now perform DNS lookups to resolve monHost, ensuring FQDN is used for OS collections when enabled.

If monHostUserNsLookup=1 (enabled) or the installer agent flag "Use nslookup to resolve the monitored hostname to FQDN" is enabled, the agent uses monHost and performs a DNS lookup, prioritizing FQDN for OS collections. The installer agent flag applies to new SQL Server agents being created.

If monHostUserNsLookup=0 (disabled or not set) and the installer agent flag is disabled, the agent follows the osUsePhysicalHostName logic:

• • osUsePhysicalHostName=1: Uses short hostname from SQL Server.
  • osUsePhysicalHostName=0: Uses monHost as-is.

Note: 

• FQDN resolution via DNS lookup requires the FglAM machine to be configured with the organization’s DNS server.
• The monHostUserNsLookup flag and installer agent option take precedence over osUsePhysicalHostName for hostname selection in OS collections.
• The monHostUserNsLookup ASP (agent status property) was added as part of the 7.3.0.10 and higher SQL Server cartridges. It is a hidden setting that cannot be updated for existing agents using the UI and requires a custom groovy script to change the setting.