btzq opened a new issue, #10164:
URL: https://github.com/apache/cloudstack/issues/10164
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Feature Idea
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
VR, Cloudstack Mgmt
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
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), 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
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
NA
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
NA
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Difficult for Cloud Operator to manage and monitor VR and the logs.
~~~
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
