Repository navigation
Centralised logging via rsyslog #4093
Description
Activity
- added a commit that references this issue
on May 27, 2020 - added a commit that references this issue
on Aug 8, 2020 @soreana are you still planning for this?
@DaanHoogland Honestly, it took a lot of time to apply the changes you required to merging this pr. I discussed it with my colleagues, and we concluded that it isn't our priority now. We focused on other stuff. It is still in our backlog, and we planned to work on it next quarter.
tnx for your efforts @soreana , i'm marking it as unplanned for now, feel free to come back at any time of your convenience.
Reacted by Sina Kashipazha@DaanHoogland Honestly, it took a lot of time to apply the changes you required to merging this pr. I discussed it with my colleagues, and we concluded that it isn't our priority now. We focused on other stuff. It is still in our backlog, and we planned to work on it next quarter.
btw, i hope they didn't sound unreasonable!?
No, they are legitimate requirements :D
@soreana should/can we mark this for 4.16?
@DaanHoogland When do you planned for 4.16 release?
this summer somewhere.
I asked our PO. We made a story to work on that. :)
Reacted by dahn3 remaining items
- added 2 commits that reference this issue
on Aug 17, 2021 Removing 4.16 milestone as PR has no milestone; let's move this back if the milestone tagging changes.
@rhtyd good 👍
Sorry for late, we got a lot of issues recently, I can't find a room to work on this pr. Maybe next week 🤞I think it may be possible via some log4j config?
I think it's possible to do this as part of a custom systemvm.iso where you can bake-in your deployment specific option. Any further update on this @soreana or we can close the issue?
- locked and limited conversation to collaborators
on Jun 5, 2024
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
Used Ubuntu 18:04 as a host for management server and KVM Hypervisor.
SUMMARY
Hello Cloudstack community. There is a systemvm remote logging feature proposal. It enabled administrator to access systemvm's log file through management server. I think it would be interesting for other as well. To better explaining my setup I depicted the configuration in below picture.
In this case rather than downloading log file manually from systemvms, they will be available automatically through management server.
STEPS TO REPRODUCE
Below are configuration files for hypervisor, management server and sytemvms.
Hypervisors
Below 4 lines have to uncommented in rsyslog configuration file on each hypervisor in
/etc/rsyslog.confAdding below file on each hypervisor to export logs from hypervisor to management server.
Management Server
Just like hypervisors, below 4 lines have to uncommented in rsyslog configuration file on management server in
/etc/rsyslog.confAdd below file on management server
Systemvm
00-fwd.conffile should add on each systemvm as well to export logs from systemvms to hypervisors.49-cloud.conffile should add on each systemvm. This file describes the logs that eventually sent to a management serverNeed to uncomment below lines if they are commented in /etc/rsyslog.conf
EXPECTED RESULTS