Beware: This is probably not supported
I was asked if I could add another syslog server to an existing VCSA deployment. With the nice blog post from William Lam in mind, adding the second server should be easy. Just edit the configuration and there you are.
The UI won’t allow this.
I guess it is CLI time then, luckily the blog post mentions this:
A minor change, but syslog-ng is no longer being used within the VCSA and has been replaced by rsyslog.
So we are just looking at a matter of finding the right config file.
In the main file
you can an “include” statement point towards the file
The only content is our first syslog server, configured as a remote syslog target.
At this point adding the second server is not a big deal, the file now looks like this:
Remember to reload the syslog service afterwards.
Another gotacha (besides the lack of support):
Changing the settings via VAMI/UI will overwrite your modifications