Hi Hari, +1. Getting log from VR is a long awaited feature.
One correction: VR does have mgmt network nic, but it doesn't have direct communcation with mgmt server(in the most case except VMware). So polling is still needed. And another comment: you can reuse CheckRouterTask() for the purpose. It already has been used for s2s vpn connection status update and redundant router checking, and "router.check.interval" would be used as interval for checking. You can improve and reuse that rather than introduce another polling thread for VR. How can you define "new alart"? Did the file would be deleted/archived after poll? Or you simply just looking after a certain point? I guess a diff works better than search for timestamp. More details in implementation would be helpful. --Sheng On Thu, Feb 13, 2014 at 1:56 AM, Harikrishna Patnala < harikrishna.patn...@citrix.com> wrote: > Hi, > > Currently in CS we can monitor the running services on Virtual Router and > ensure they are running through the lifetime of VR. Upon failure of any > service in VR, monitoring service logs the alerts in VR logs. > These alerts need to be pushed to management server to notify admin. > > For this I'd like to introduce the feature Virtual Router service failure > alerting. > > [1] https://issues.apache.org/jira/browse/CLOUDSTACK-6090 > [2] > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Virtual+Router+Service+Failure+Alerting > > > Comments/feedback are welcome > > Thank you, > Harikrishna >
