Configure Data Collector

A Data Server can be run as a Data Collector (or "sender"), which sends monitoring data to a target Data Server (or "receiver"). Data Collectors are useful for distributed deployments, to collect data from otherwise unreachable brokers, as well as for large deployments, to spread the load of data collection between processes. Multiple Data Collectors can all send data to a single Data Server, which aggregates all data into the same data caches.

To run a collector:

1.

Install Solace PubSub+ Monitor on a system that can access not only the Solace brokers that you wish to monitor but also the system running the data server you wish to send the data to.

2.

Start the collector:

–

cd bin

–

Run the start_tomcat(.sh or .bat) script.

–

Run the start_collector(.sh or .bat) script.

3.

Configure your Collector connections:

–

Browse to the following URL and login (rtvadmin/rtvadmin) to open the RTView Configuration Application HOME page:

http://IPAddress:8068/rtview-solmon-collector-rtvadmin

–

Select the Solace Monitor - Data Collector project to open the Solace configuration page.

–

Select Solace in the navigation tree (left panel), then click the + icon to add a broker connection.

Tip: Gray text shows the default setting for the field which you can edit. To return to the default setting, delete the text you entered.

–

In the Add Connection dialog do the following:

–

Toggle ON Edition if your broker is a PubSub+ Event Broker as a service instance.

–

For Cloud Service Brokers, enter the Connection Name, URL, Username, Password, SEMP Version* and VPN Name. Turn on the SSL Connection toggle if your broker is SSL Secured. See Obtain SEMP Version for instructions about getting the SEMP version installed in your message brokers.

–

For Non-Cloud Service Brokers, enter the Connection Name, Host:Port, Username and Password. If the broker is secured, the URL should use https instead of http.

–

If you are connecting via SSL, toggle ON SSL Secured, select SECURITY (in the navigation tree) and fill in the SSL Credentials section with the appropriate Truststore Location and Truststore Password values for your Brokers.

–

Repeat these steps to add more brokers and when finished, click SAVE to close the dialog and SAVE (in title bar) to save your settings. The connections you created are listed in the Connections tab.

–

Click SAVE and then RESTART SERVERS to apply changes. The collector will be available again in 10-15 seconds.

4.

(Optional) Verify your Collector Connections:

You can verify your data connections by enabling the Data Collector's internal Jetty HTML Server.

–

In the Data Collector Configuration Application, select Data Server in the navigation tree (left panel)

–

Toggle on HTML Server Enabled.

–

Click SAVE and then RESTART SERVERS to apply changes.

–

Browse to your Data Collector's Cache Viewer using the following URL:

http(s)://IPAddress:4170/common

The RTView Cache Viewer application allows you to view the details for the caches that are collecting data.

 

5.

Connect the (sender) Data Collector to a target (receiver) Data Server:

Prerequisite(s): These steps assume you have already installed, and are running, the Data Server you wish to send data to.

–

Navigate to Server Configuration > Data Server > Collector tab.

The Collector tab displays with a default target1 already created. This target is configured to send all solution package data to localhost:4172, 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.

–

To edit the existing target, click the "pencil" icon associated with the target. The Edit Target window displays.

–

Define the target server information and click SAVE where:

–

ID: The name you want to give to the target server.

–

URL: The complete URL for the target server connection.

Note: If the target Data Server is configured as High Availability, use an HA URL in the Target field of the Configuration Application, ex. primaryhostname:4172,backuphostname:4172. See Configure HA for more information about this configuration.

–

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.

–

Click SAVE in the title bar and RESTART SERVERS to apply changes. The collector will be available again in 10-15 seconds.

6.

Verify your Target Configuration:

Browse to your Solace PubSub+ Monitor's (the target Data Server's location) and login:

http://IPAddress:8068/rtview-solmon 

If your configuration was successful, monitoring data from your data collector will appear in Solace PubSub+ Monitor.