The RTView DataCollector for Infrastructure collects Solution Package data via connections that you define in the RTView Configuration Application and sends the collected data to the RTView DataServer for Infrastructure, which collects this data and any additional data that the RTView DataServer for Infrastructure is collecting. This collected data is then pulled into RTView Cloud via an RTView Data Server connection created in RTView Cloud. Note that the RTView Data Collector does not generate alerts or store history data.
This document describes how to download and install the RTView DataCollector for Infrastructure for use with RTView DataServer for Infrastructure and RTView Cloud, how to configure the data collector including defining the connection information for each solution package (Docker, MongoDB, and so on), how to connect to the RTView DataServer for Infrastructure, and how to verify that your setup is working properly in the RTView DataServer for Infrastructure. This document assumes that you have already downloaded and installed the RTView DataServer for Infrastructure. See RTView DataServer for Infrastructure Quick Start Guide for more information.
Note: If you are interested in setting up High Availability (failover) for your DataCollector, review Configuring High Availability for DataCollector Deliverables prior to starting this flow.
Note: In addition to using the RTView Configuration Application for configuring your connections, you can use the Property Editor REST API to import initial connections or automate connection updates. See Property Editor REST API for more information.
Amazon Web Services connections: Location of your .jar files, the Access ID Key, the Secret Access Key, and the fully qualified name for an Amazon Service (Cloudwatch) that provides monitoring data.
Docker connections: Verify cAdvisor is set up properly and know the desired port to use if different from the default port.
Microsoft SQL Server connections: Connection name, URL for the SQL server, and username/password (if specified).
MongoDB connections: Connection name and URL to each MongoDB to which you want to connect.
MySQL connections: Connection name, database URL, and username/password (if specified).
Node.js connections: Know the desired port to use if different from the default port.
RTView Host Agent connections: All configurations are optional.
RTView Manager connections: Connection name, host name/IP address of the MBean server, port exposed by your MBean server, and username/password (if specified).
RedHat JBoss connections: Connection name, URL for the connection, and username/password used for the connection (if specified).
VMWare connections: Connection name, connection method (vCenter Server or Direct EXSi Host), URL for the connect method, and username/password (if specified).
Log in to your RTView Cloud account at http(s)://rtviewcloud.sl.com.
If you do not have an RTView Cloud account, go to http(s)://rtviewcloud.sl.com/register and follow the instructions to create your account.
Note: If you log in using https, you must use https for your data server links as well. If you log in using http, you can use http or https for your data server links.
Once you have logged in, RTView Cloud displays.
The RTView Cloud Support Home page displays.
Click the Downloads button.
The RTView DataServer Downloads page displays.
Scroll down to the RTView DataCollector for Infra region and click the Terms and Conditions link to view the SL Corporation - End User License Agreement, click the I agree to the Terms and Conditions check box, and then click the Download RTView DataCollector for Infra button.
The compressed file is saved to your machine.
When you install the DataCollector, a temporary license key is included. SL Corporation will send you a permanent key that you will need to add to your RTView license key file so that you can extend the operation of your monitoring system.
This is a universal key that will enable you to run RTView on different machines and platforms. It is your responsibility to ensure you use RTView within the terms of your End User License Agreement (EULA).
To update your RTView system with your new license key, open a command window and:
Note: If using UNIX, do not include spaces in your installation directory path. The start_server.sh and stop_server.sh scripts will not function properly if spaces are included in the installation directory path.
Extract All (Windows)/unzip (UNIX/Linux) the file to the directory of your choice. For UNIX/Linux, use unzip -a to unzip the file.
Open a command window and set the JAVA_HOME environment variable to point to your Java Installation. For example:
export JAVA_HOME=/opt/Java/jdk1.7.0 (UNIX/Linux)
set JAVA_HOME=C:\Program Files (x86)\Java\jre1.8.0_201 (Windows)
Or, in Windows, you can set JAVA_HOME as an environment variable (in Control Panel > System > Advanced system settings), where it will then be used by all command windows and when you double-click on a .bat file.
start_collector.bat (Windows)
./start_collector.sh (UNIX/Linux)
Or, in Windows, you can double-click on the start_collector.bat file in the RTViewDataCollectorInfra directory.
Note: This script starts the Data Server on port 3278 with HTML Server (Eclipse Jetty, by default) on port 3270. If these ports conflict with other processes running on your system, you can change the first two digits of the ports by using -portprefix: and specifying the first two digits you want to use for the ports in the command line. For example: start_collector.bat -portprefix:44 (which would change the ports to 4478 for the Data Server and 4470 for HTML Server). If you want to save your port prefix, you can change the port prefix in the RTView Configuration Application (see the next section), or you can use -saveportprefix: command line argument (for example: start_collector.bat -portprefix:44 -saveportprefix).
Next, you need to specify the directory path to your .jar files and you need to create your connections for the each of your solution packages using the RTView Configuration Application.
http(s)://localhost:3270/rtvadmin (for a local installation using Eclipse Jetty)
http(s)://<IP address>:3270/rtvadmin (for a remote installation using Eclipse Jetty)
Note: If you specified a different port at startup (due to a port conflict), you must use the port you specified in the command line. For example, if you specified 44 as your port prefix in the command line at startup, then you would use:
http(s)://<IP address>:4470/rtvadmin
The Authentication required dialog displays.
The RTView Configuration Application displays.
The RTView Configuration Application displays with the General tab open.
Data Cache: No configuration necessary.
RTView Host Agent: No configuration necessary.
User Experience: No configuration necessary.
Next, you need to connect the RTView DataCollector for Infrastructure to the RTView DataServer for Infrastructure. To connect the two servers:
The Collector tab displays with a default target1 already created. This target is configured to send all solution package data to localhost:3272, which only works if your data collector and data server are on the same machine. If your data server is on a different machine, you will need to edit this target.
The Edit Target window displays.
ID: The name you want to give to the target server.
URL: The complete URL for the target server connection.
Targets: Select one of the options:
All solution packages: (default) Sends all solution package data to the target (receiver) data server.
Select solution packages: Opens the Solution Packages dialog that allows you to select the solution packages for which you want data sent to the target (receiver) data server.
Enabled: Enables/disables the target connection.
stop_collector.bat (Windows)
./stop_collector.sh (UNIX/Linux)
start_collector.bat (Windows)
./start_collector.sh (UNIX/Linux)
To verify your setup:
http(s)://<IP address>:<port>/common
For our example, we changed the port to have a prefix using 44 and we have a local installation, so our URL is:
http://localhost:4470/common
The RTView Cache Viewer application displays, which allows you to view the details for the caches that are collecting data.
http(s)://<IP address>:<port>/common
For our example, we used the default port prefix and we have a local installation, so our URL is:
http://localhost:3270/common
The RTView Cache Viewer application displays, which allows you to view the details for the caches that are collecting data.