Thomson Reuters RTDS

Overview Copied

Geneos configuration templates are available for monitoring the Thomson Reuters Real-Time Distribution System (RTDS) platform. The integration provides a set of configuration files, dashboards, and tools that enable out-of-the-box monitoring of the RTDS platform and related applications through preconfigured Managed Entities and types.

Package Contents Copied

The integration package geneos-integration-rtds-<version>.zipcan be downloaded from ITRS Downloads site and contains the following:

Installation Copied

Below are the steps to use the Gateway include files:

  1. Open up the Gateway Setup Editor.
  2. In the Gateway Setup Editor, right-click on the Includes folder and then select  New Include.
  3. Change the Priority to any value other than 1.
  4. In the Location field, enter the path of the include file that is in the binary package.
  5. Variables are pre-defined in the environments for each component. If you wish to change the variables, then go to Operating EnvironmentsVar.
    • If you are using RTDS.xml, then you need to define the following variables:

RTDS variable

Variable Definition Default
REFINITIV_BASE Base directory of the RTDS installation. /opt/refinitiv
LogPath Full path to the log directory of your components. /opt/refinitiv/log
RMDS_CONFIG Subpath and the file name of your central config file. The value of this variable gets appended to the value of the REFINITV_BASE variable. /SOFTWARE/globalconfig/rmds.cfg
rifFilePath Directory where the RMC interface files are located.


Note: If not changed, the RMC interface files will be written in your Netprobe directory.

Probes Copied

If you are using the GLOBAL_Geneos.xml, you will find a virtual probe in the Gateway Overview Managed Entity. This contains virtual self-monitoring for the Gateway with samplers for probes, client connections, data age, and many more.

Gateway overview

Similarly, you will also find a virtual probe in the RTDS Overview Managed Entity. The RTDS Overview Managed Entity assembles data for the dataview but also works very well as a platform overview in itself. All of these are driven by the pre-defined types, so even if you are not using the included Managed Entities, the dataviews should not be affected.

RTDS Overview

Types Copied

The GLOBAL_Geneos.xml and RTDS.xml include files have pre-defined types in the configuration.

Types in GLOBAL_Geneos.xml include file Copied

Geneos XML include file

For hardware monitoring, all the types include process and logfile monitoring for a Netprobe,

The types in the Infrastructure folder cover the recommended baseline monitoring. The main type used is the Infrastructure Defaults which provides samplers for Disk, CPU, Network, and TOP plugins.

If you wish to monitor a Gateway host, then you must include the types in the Application folder as appropriate.

Types in RTDS.xml include file Copied

RTDS XML include file

All types in the RTDS.xml include file contains standard samplers for Info, License, Processes, and Logfiles.

For application monitoring, the following types are typically in use:


For standard DACS application monitoring, you need to run a separate DacsTrans binary, which is included in the /bin/tran directory.

For intrusive DACS monitoring, the Netprobe should run with the relevant Oracle or PostgreSQL client libraries loaded.

For all types in the ADH and ADS folders, there is a TCP-Links sampler monitoring for the ports 8101/14002 either remotely for ADH/POP or locally for ADS/POP.

For any standard ADH or ADS, you can add the RRCP-Sink and RRCP-Source types for monitoring the RRCP layer when running a standard RRCPD.


For standard RRCPD application monitoring, you need to run a separate RrrcTrans binary, which is included in the demo directory.

If you are running a daemon less RRCP, then the HSM-Source, HSM-Sink, or HSM-Standby types are recommended. The statistics are in the shared memory of the main component and you do not need to run any Trans process.

For DACS application monitoring, you may use the types in the DACS > Station, DACS > Server, and DACS > SinkDaemon folders. The included types cover database monitoring for PostgreSQL or Oracle databases, and intrusive DACS monitoring. When doing map collects, these samplers will also provide an overview of any new PE sets before distribution.


 For standard DACS application monitoring, you need to run a separate DacsTrans binary, which is included in the /bin/tran directory.

For intrusive DACS monitoring, the Netprobe should run with the relevant Oracle or PostgreSQLclient libraries loaded.

Commands Copied

You can interact with your RTDS through Geneos by using some of our built-in commands. Whilst these may be handy, we urge you to consider restricting use for a wider audience by using authentication.

For all samplers, the usual default Geneos commands are available as applicable. The following are some of the built-in commands included in the RTDS.xml include file:

Dataviews Copied

The include files contains many samplers, in return, there could be many dataviews that can be displayed in the Active Console. The following are some of the views that you can use:

Dashboards Copied

The downloaded binary package includes the following Active Dashboard files: RTDS1.adb and RTDS2.adb.

If you are using the RTDS.xml include file, then the Dashboard attribute is set as <attribute name="Dashboard">RTDS1</attribute>, and the data from your Gateway will be displayed in the RTDS1.adb Active Dashboard.

If you are using a second Gateway, then set the Dashboard attribute as <attribute name="Dashboard">RTDS2</attribute>, which will display the data from your second Gateway in the RTDS2.adb Active Dashboard.

The following is an example that shows what the Active Dashboard looks like:

Dashboard example

["Geneos"] ["Geneos > Netprobe"] ["User Guide"]

Was this topic helpful?