I am familiar with how to configue syslog in the UI and command line. We have it working in vSphere 5.5 and it goes to a remote server using the separate component install for Syslog. vSphere 6.5 has changed all that and for the likes of me I can not get it working and forwarding to a remote server. I am not even sure if this is still supported but I did manage to get it using the local disk as I can do a du -h and see a syslog server there and /var/logs pointing to it as well with ls -lha.
Any ideas how I can configure Syslog to point to a new server running Server 2016? For hosts I tried udp://<destination>:514. Firewall is open for Syslog and off by default.
William Lam has a few articles out there for SysLog but some have disclaimers.
https://www.virtuallyghetto.com/2017/02/what-logs-do-i-get-when-i-enable-syslog-in-vcsa-6-5.html
https://www.virtuallyghetto.com/tag/sysloghttp://https://www.virtuallyghetto.com/2017/02/what-logs-do-i-get-when-i-enable-syslog-in-vcsa-6-5.h...
This is the one with the disclaimer saying it is not supported
I am confused
Are you asking how to configure vCenter 6.5 installed on Windows to point to a new syslog server, or pointing the vCSA 6.5 to a Windows Server 2016 running syslog server? For the latter, it's a simple trip into the VAMI.
Thanks. I want to point logs to the remote host running Server 2016. I realise this exists in the VamI. However I don't understand something. It only accepts fqdn or an ip. What is the path then? On hosts you specify a path or datastore.
Because syalog is a network protocol, not a file path. And ESXi hosts have the same ability.