I am fairly certain that it is required to have the logger package installed somewhere in your suite. With out it not only will you not get the obvious logging of data on your nodes, but you will also not get the status page of all your servers on the admin console. I am thinking that it could potentially have adverse effect on the admin console and perhaps your suite. Moving the logger node to another host is also relatively painless. I have done it on my production and testing suite. I also wrote the procedure for it that Adam Cody posted on his notes on the zimbra wiki.
I hope that helps.
From: "Tim Ross" <tross@calpoly.edu>
To: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Thursday, May 16, 2013 7:26:19 PM
Subject: Zimbra Logger Server
We are in the planning phases of virtualizing all of our Zimbra environments. As we are looking at space requirements and making a few changes to our setup, we started wondering why we were keeping our Zimbra Logger server around. We have had one since we started with Zimbra, but have never used the combined logs that are gathered on it. The logs on the single servers themselves are busy enough on their own, so the combined logs of multiple servers are that much harder to sift through. Zimbra Support has never asked us for the logs from this server when we have been troubleshooting issues. We have other monitoring tools and a central campus logging server for our Audit log info. So, this leads me to my question for you. Do any of you actually use the logger server for any special functions?
Thanks for your input.
Tim Ross
Application Administrator
Enterprise Applications Group
Cal Poly State University, San Luis Obispo
(805)756-6226