You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2021/08/10 14:40:32 UTC

[GitHub] [cloudstack] DaanHoogland commented on pull request #5296: [WIP] Centralized logging capability. Follow up on the #4108

DaanHoogland commented on pull request #5296:
URL: https://github.com/apache/cloudstack/pull/5296#issuecomment-896087473


   @soreana You are asking a rather wide question but let me try;
   I'd create global settings for
   - remote logging for VRs
   - remote logging for systemVMs
   - remote logging for hosts
   Than based on these settings appropriate changes on the targets can be made
   as for the management server, I'd say that a separate package setting up the remote log server should be installed, this should already exist in most linux distros. Worst case a dependency can be defined and some minor post install script run (i.e. cloudstack-logserver-4.16.0.0.rpm)
   
   Most operators will want to make it a different machine than the management server.
   
   The IP of the remote logging server should be configurable per target as one can have a rather various cloud topography. An alternative would be to install a pass-through logging server that redirects to a central server, but that is only for the advanced version.
   
   I'm pretty sure I didn't answer (all of) your questions but I hope I contributed some.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org