Does anyone out there know the reason why VMware removed the vi-logger functionality out of the vMA appliance in vSphere 5?
I can understand adding an easy to use facility on vCenter as this is a great solution for SMB, but for large corporate's I wouldn't use it as it adds an unnecessary level of complexity for the vCenter server. Think upgrading or reinstalling vCenter servers in a linked mode environment with hundreds of hosts. Needing to add and setup that functionality for logging adds a extra couple of hours to a change that I would really rather not have to do.
Also many of the corp or Gov environments I work in have syslog setups, but setting it up requires communicating and liaising with other teams who are often not helpful or co-operative. Having a dedicated syslog system for VMware Admins makes life so much easier but as above I don't want it on my vCenter server and I don't want to pay for another Windows license just to get the seperation I'm looking for.
I've seen the the virtuallyGhetto post about re-enabling vi-logger in vMA 5.0 which is great and I'll probably do a blog at some point similar to my end-to-end walkthrough for setting up a vMA 4.1 syslog server. But I would really like to know the logic behind disabling vi-logger in vMA 5.0. Also if people start re-enabling this functionality in vMA 5.0 does that mean VMware will break future releases so that you can't? That would be crazy annoying.
Cheers,
Paul