The panagenda GreenLight backend does several tasks to optimize its performance and ensure its availability.
Housekeeping tasks are:
Data Staging and Optimization
panagenda GreenLight's backend database is structured in several "stages" to keep its stored data at a high availability level and make sure that access to reports and charting is always at best performance.
The maintenance of these stages occurs daily, between 0 am and 2 am in the morning. In this time, the CPU and hard disk utilization of the panagenda GreenLight appliance could significantly increase and access to reports and charts could take longer than normally experienced.
The current staging schedule is:
• TCP, UDP and ICMP sensors: 0:20 am
• HTTP Access Sensor 0:30 am
• Availability Index 0:40 am
• Cluster Database Access 0:40 am
• Traffic Analysis (Mail and Replication) 0:45 am
• Database Access 0:50 am
• Log Analysis 1:00 am
• Sametime 1:20 am
• SNMP 1:40 am
• Domino Statistics 2:00 am
Please note that these schedules indicate the start time of the database staging. Finishing time depends on the amount of collected data within the last staging cycle.
Heartbeat
panagenda GreenLight maintains a heartbeat log to validate that panagenda GreenLight itself is still up and running. A simple file (default location is /opt/tomcat/logs/heartbeat.log) is updated every five minutes with a timestamp of the actual appliance date and time.
The timestamp within this file should never be older than five minutes. Timestamps older than five minutes indicate a panagenda GreenLight runtime problem.
Automatic Restart-on-Fail Feature
An internal job checks hourly if the heartbeat file is regularly updated. If the timestamp within the heartbeat file is too old, after a short time period the job reads the timestamp again (approximately 30 seconds). If the timestamp in the heartbeat file is still older than 5 minutes, the job assumes a permanent system failure and restarts the panagenda GreenLight virtual appliance.
You can disable the automatic restart feature by removing the appropriate line from the job scheduler configuration file (/opt/panagenda/scripts/greenLight-cron.hourly)
We strongly recommend to let this feature enabled unless you use other ways to monitor the availability of panagenda GreenLight.