The Email Address to be used as the senders Email for the Notification Email.If left blank, Cacti will use the default Automation Notification Email Address if specified, otherwise, it will use the Cacti system default Email Address
When you setup the right axis labeling, apply a rule to the data format.Supported formats include "numeric" where data is treated as numeric, "timestamp" where values are interpreted as UNIX timestamps (number of seconds since January 1970) and expressed using strftime format (default is "%Y-%m-%d %H:%M:%S").See also --units-length and --right-axis-format.Finally "duration" where values are interpreted as duration in milliseconds.Formatting follows the rules of valstrfduration qualified PRINT/GPRINT.
When you setup the left axis labeling, apply a rule to the data format.Supported formats include "numeric" where data is treated as numeric, "timestamp" where values are interpreted as UNIX timestamps (number of seconds since January 1970) and expressed using strftime format (default is "%Y-%m-%d %H:%M:%S").See also --units-length.Finally "duration" where values are interpreted as duration in milliseconds.Formatting follows the rules of valstrfduration qualified PRINT/GPRINT.
<strong>NOTE:</strong> You are logged into a Remote Data Collector.When <b>'online'</b>, you will be able to view and control much of the Main Cacti Web Site just as if you were logged into it.Also, it's important to note that Remote Data Collectors are required to use the Cacti's Performance Boosting Services <b>'On Demand Updating'</b> feature, and we always recommend using Spine.When the Remote Data Collector is <b>'offline'</b>, the Remote Data Collectors Web Site will contain much less information.However, it will cache all updates until the Main Cacti Database and Web Server are reachable.Then it will dump it's Boost table output back to the Main Cacti Database for updating.
On rare occasions, we have had reports from users who experience some minor issues due to changes in the code.These issues are caused by the browser retaining pre-upgrade code and whilst we have taken steps to minimise the chances of this, it may still occur.If you need instructions on how to clear your browser cache, <a href='https://www.refreshyourcache.com' target='_blank'>https://www.refreshyourcache.com/</a> is a good starting point.
YOU MUST MANUALLY CHANGE THE CACTI DATABASE TO REVERT ANY UPGRADE CHANGES THAT HAVE BEEN MADE.<br/>THE INSTALLER HAS NO METHOD TO DO THIS AUTOMATICALLY FOR YOU
When using MariaDB 10.2.4 and above, this setting should be off if atomic writes are enabled.Therefore, please enable atomic writes instead of the double write buffer as it will increase performance.