7.3 Reporting and Monitoring Configuration
Retain comes equipped with a separate Reporting and monitoring server. Reporting and Monitoring may be installed on the same or a different physical or virtual machine as the Retain Server.
Reporting and Monitoring functions much like the Retain Worker in that it is installed as a separate entity and requires connection information from the Retain Server. Additional security is provided through the option to specify exactly which IP address(es) the Retain Server will allow a connection from. Separate with commas the IP addresses allowed if more than one. No mail data is transferred through this connection, only server statistic information.
7.3.1 Setup
The Core Settings, Logging, Connection and Notification sections of Reporting and Monitoring configuration work identically to the Worker connection settings, and should be filled-out accordingly. Most server implementations will require little to no modification to these settings save the notification tab. Limiting the server connections to specified IP Addresses limits which machines have access to the Reporting and Monitoring module. Separate multiple addresses with a comma.
Putting a checkmark in the ‘Do not expire inactive sessions’ will allow sessions with the R&M module to never expire. This is useful in conjunction with the ‘monitoring’ page.
Selecting the ‘Disable the disk usage statistics’ box will disables the ‘archive size’ from server utilization report. Selecting ‘Disable the number of messages statistics’ disables the ‘total messages stored’ on the Reporting and Monitoring dashboard. These options are for systems which encounter a bottle-neck which impacts system performance with these checks.
Set the logging level to the desired setting. Leaving the logging as default ‘normal’ is recommended unless instructed to increase the logging level by Support.
The Connection between Reporting and Monitoring, and the Retain Server should not be changed unless the Retain Server requires a modified connection path, (such as a custom port.)
The R&M server is different from the Retain Worker in that the Retain Server is able to contact the R&M server as well. The connection address to R&M should not be modified unless custom connection settings have been created.
The connection from the Browser to the R&M Server is how the browser is going to connect to the R&M server when redirected from links in the Server. This connection information needs to be accurate for where the R&M Server is installed and listening.
When configured to use HTTPS, the web server must be configured to use a full TLS certificate chain signed by a trusted third party Certificate Authority, not self-signed, and configured with both server and intermediate certificates.
Notification defaults to the standard notification address specified in the Retain Server activation and initial configuration. If the notification is desired to be different, modify the settings here. Make sure to test the connection to ensure proper function.
Like the Retain Worker, the R&M server must be uploaded a saved configuration or ‘bootstrap’ file. To access this tab, the configuration must be saved first. Then the bootstrap tab will become available. Download the file to a known location and then browse to the R&M server webpage. The default connection address is shown on the connection tab.
From the R&M initial webpage, click on the “Browse” button and browse to the saved bootstrap file and select it.
Click ‘Continue’ to upload the bootstrap file. As the bootstrap file is uploaded, R&M functions will become available. Only users with the administrative “Access Reporting and Monitoring Server” right will be able to login to the stat server.
To log into the R&M server, select the ‘Reporting’ or ‘Monitoring’ links from the Retain Server left menu to spawn a new tab or page to the R&M module.