This is an automated email from the ASF dual-hosted git repository.

andrijapanic pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/master by this push:
     new a8353cc  [WIP] updates to service monitoring script (#88)
a8353cc is described below

commit a8353cce4f303bf2cac8810a883368a66b4f9c40
Author: Andrija Panic <[email protected]>
AuthorDate: Fri May 1 18:19:36 2020 +0200

    [WIP] updates to service monitoring script (#88)
    
    * [WIP] updates to service monitoring script
    
    * Update systemvm.rst
    
    * updatenotes
---
 source/adminguide/systemvm.rst | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/source/adminguide/systemvm.rst b/source/adminguide/systemvm.rst
index 4c3da98..cc79004 100644
--- a/source/adminguide/systemvm.rst
+++ b/source/adminguide/systemvm.rst
@@ -385,17 +385,17 @@ an unexpected reason. For example:
 .. note:: 
    Only those services with daemons are monitored. The services that are 
    failed due to errors in the service/daemon configuration file cannot 
-   be restarted by the Monitoring tool. VPC networks are not supported.
+   be restarted by the Monitoring tool.
 
 The following services are monitored in a VR:
 
--  DNS
+-  DNS (dnsmasq)
 
--  HA Proxy
+-  HAProxy (haproxy)
 
--  SSH
+-  SSH (sshd)
 
--  Apache Web Server
+-  Apache Web Server (apache2)
 
 The following networks are supported:
 
@@ -403,11 +403,16 @@ The following networks are supported:
 
 -  Shared Networks in both Advanced and Basic zone
 
-   .. note:: VPC networks are not supported
+-  VPC (as of CloudStack 4.14)
 
 This feature is supported on the following hypervisors: XenServer,
 VMware, and KVM.
 
+Log file /var/log/routerServiceMonitor.log contains the actions 
undertaken/attempted by the service monitoring script (i.e. trying to restart a 
stopped service).
+
+As of CloudStack 4.14, the internval at which the service monitoring script 
runs is no more hardcoded to 3 minutes, but is instead controlled via global 
setting router.health.checks.basic.interval.
+
+
 
 Enhanced Upgrade for Virtual Routers
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Reply via email to