Article Contents
Large up.time deployments may achieve performance benefits by transferring up.time reporting functions to a dedicated reporting instance that only generates and serves reports. System monitoring involves intensive insertion of data into the up.time DataStore and running reports over long date ranges and many systems can require a large number of DataStore requests. Most of the larger up.time deployments where this becomes a concern are already using an external database like SQLServer or Oracle, which provides plenty of capacity within the database. So by distributing uptime’s activity across two instances, we’re able to use more of this capacity then we could with a single instance. If you are considering deploying an up.time reporting instance in your environment, please contact support beforehand. So that we can help assess if a remote reporting instance will help in your environment. Reporting Instance Architecture An up.time deployment with a reporting instance has 2 separate up.time installations:
Both installations will connect to the same database backend. The following graphic illustrates the relationship between the monitoring station and reporting instance: Note the following:
Step 1 - Install the Reporting Instance This step assumes that the monitoring station is already installed and collecting data. The reporting instance will be installed as a new copy of up.time on a separate server. Before installing the reporting instance, ensure that the server that will host the reporting instance supports the minimum hardware and operating system requirements for an up.time monitoring station. For more information on sizing and installing a monitoring station, see Recommended Monitoring Station Hardware. Note: The operating systems of the two hosts can be different. However, the up.time version must be the same for both the monitoring station and the reporting instance. Step 2 - Configure the Reporting Instance Settings To enable a separate up.time reporting instance, configuration settings must be changed on the monitoring station and additional configuration options must be added to the uptime.conf file on the reporting instance. On the reporting instance, add the following entry to the uptime.conf file to disable all non-reporting functions: reportingInstance=true We also need to scale down the size of the connectionPoolMaximum in the uptime.conf from the default option of 100 to 50: connectionPoolMaximum =50 Also refer to the Mail Server settings on your monitoring station and copy the settings into the uptime.conf file on the reporting instance to enable it to send reports via email: smtpServer=mail.yourserver.com smtpPort=25 smtpUser=username smtpPassword=password smtpSender="uptime Monitoring Station" In the smtpSender entry, you can change uptime Monitoring Station to another value such as up.time Reports. Login to the web interface of the monitoring station. In the navbar, click Config and then click Remote Reporting in the left side menu. Click the Edit Configuration button to open the following window: Edit the following fields:
Step 3 - Verify the Monitoring Station can Access the Reporting Instance After you have set up the monitoring station and reporting instance, verify that the two instances can communicate with each other:
Step 4 - Published Reports Folder changes Now that the remote reporting instance has been successfully setup, and we’ve confirmed that the monitoring station is able to push report generation requests to the remote server. We need to make changes to accommodate the change in the ‘Published Reports’ folder. As mentioned in the Architecture section above, all published reports are now saved on the reporting server, instead of locally on the monitoring station like before. That means we have two options for howto handle this change:
Additional Steps using the Bundled MySQL Datastore with Remote Reporting The above steps for setting up a remote reporting instance were tailored for environments where the up.time datastore is running in an external database like Oracle or SQLServer. It is possible to setup a remote reporting instance that connects to the bundled mysql datastore service on the monitoring. The potential performance boost won’t be as large as compared to using an external database. The reason for this that the bundled mysql datastore still runs on the monitoring station, and shares resources with the main uptime instance. Using an external database means that there is already a database user available with Read/Write access, as well as a larger database connection pool available. So in order to use the bundled mysql datastore with the reporting instance, we’ll need to take some additional steps to account for this.
Granting the uptime database user external access:
Increasing the max_connections on the bundled mysql instance:
|
Creating custom reports with Microsoft Reporting Service | Rating | Views | |
---|---|---|---|
Learn how to query data from an MS SQL Server DataStore and create reports with Microsoft Reporting Services. By: uptime Support | Date Created: 1-3-2007 | Last Modified: 7-6-2011 | Index: 113 |
8173 |
How to verify the Active Directory Domain Name setting | Rating | Views | |
---|---|---|---|
- Logon to a Windows system that is on the domain - Open up the command line (Start > Run > cmd) - Type the following: > net config workstation - Enter the value for "Logon Domain" into the uptime... By: uptime Support | Date Created: 10-7-2009 | Last Modified: 8-13-2011 | Index: 388 |
3040 |
ESX Instance Workload Data | Rating | Views | |
---|---|---|---|
This article outlines the metrics that up.time collects from the instances on ESX systems. By: uptime Support | Date Created: 1-23-2007 | Last Modified: 7-4-2011 | Index: 120 |
5540 |
ESX instance Percent Used > 100% | Rating | Views | |
---|---|---|---|
You may notice alerts from the ESX Workload monitor indicating that the Percent Used for a specific VM instance is greater than 100%. This is a valid scenario indicating that the instance is using... By: uptime Support | Date Created: 6-26-2010 | Last Modified: 8-10-2011 | Index: 455 |
1732 |
VM instance is consuming a license | Rating | Views | |
---|---|---|---|
There are several reasons a VMware instance may consume a license. 1) VMware tools are not installed on the target VM. 2) The VM is not running on an ESX server that is also monitored by up.time... By: uptime Support | Date Created: 8-7-2010 | Last Modified: 5-4-2013 | Index: 470 |
1736 |