Not ALL .Net Alarms can include host names
Some rules cannot have hostname at all because the topology type, NETRequestType does not have hostname associated to it.
There is an update of the current build (18.104.22.168) that fixed any rules that could have hostname associated but did not. The list of rules that have hostname associated are as follows. Please open a support case if you wish to have the updated build for 22.214.171.124 if the following rules do not have hostname in the rule message.
• .NET Server Memory Usage Checking
• .NET Server Performance Amount Exceeded
• .NET Server Data Uptime
• .NET Server Exception Amount Exceeded
• .NET Server Event Execution Time Trend
• .NET Server Request Time Threshold
• .NET Server CPU Usage Checking
• .NET GC High Load
• .NET Application Exception Amount Exceeded
• .NET Application Performance Amount Exceeded
• .NET Application Event Execution Time Trend
• .NET Application ASP Request/sec Threshold
• .NET Application Event Execution Time Threshold
Any rules scoped to NETRequestType cannot.
• .NET Event Application Failure Threshold
• .NET Event Connectivity Threshold
• .NET Event Execution Time Threshold
• .NET Event Execution Time Trend
• .NET Event Security Threshold
to a host.
DN-32 to handle the request to add hostname to all Rules/Alarm messages.
DN-34 is specifically to update the NETRequestType object to associate hostname.