so thanks the problem has been solved
fill this field : syslog.global.loghost with
hostname means log insight
1 person found this helpful
You might also find that if you already had an ESXi host configured with Log Insight and are redeploying you could run into this issue as well. Simply edit the host configuration for this entry: syslog.global.loghost with
tcp://hostname:514 and delete the value and save as blank. Go back into Log Insight and reconfigure the host, success.
Experiencing this problem with following environment
vRealize Log Insight Manager : 4.7.1
vCenter : 6.7
vSphere : 6.5
In this case host doesn't accept the change in value of "Syslog.global.logHost" , has anybody else seen this issue.