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
Difficult for Cloud Operator to manage and monitor VR and the logs.