Repository navigation
Virtual Router to output logs to Cloudstack Mgmt Server, so Operator can monitor via Zabbix, Loki or other system #10164
Description
Activity
@btzq , this is not the first time this comes up. There have been implementation attempt on this as well. Maybe it is good to have a discuss item to discuss how this would be implemented and how configurable it would be. (https://github.com/apache/cloudstack/discussions/new/choose)
I see @DaanHoogland , then can you help convert this ticket to a discussion?
We can continue discussions there.- locked and limited conversation to collaborators
on Jan 6, 2025
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
When a VR is created, the logs are only being output within the VM, which makes it very difficult to monitor.
When an issue occurs, it is likely the cloud operator would reboot or clean up the router, resulting the VR being recreated and logs being lost. But this is done to restore the services with as little downtime as possible.
It would be great to have the VR output logs back to a central location in Cloudstack Management. Then, using some sort of log monitoring tool (Zabbix, Grafana Loki, Wazuh SIEM), we can monitor logs of all VRs created to lookout for key words which may signify an issue.
This can also lead to potential future automations such as: 'If Keyword exist, cleanup VPC' via some self built automation service that talks to Cloudstack APIs.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS