- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.