The RMC plug-in brings RMC variables of any Refinitiv market data system (TREP) component seamlessly and in real-time into the Geneos environment. When integrated, these parameters become fully manageable.
In addition to translating RMC variables, the RMC plug-in provides additional value added functionality such as:
- The ability to pick and display selected RMC variables, removing the complexity of the built-in tools (adhmon, adsmon).
- Provide rate of change calculation. Actual values of some of the parameters, such as the total number of updates, for example, are irrelevant by themselves. The rate of change of those parameters is much more useful.
The template section is used to pick and display the desired variables. You can select from two modes:
- data — enables you to pick and display RMC variables, as desired.
- Rmc template — enables you to reuse an existing data template into a new RMC Interface sampler.
When you opt for the data option, you can define the dataview from scratch:
This section defines up to six headline-type variables that are shown at the top of the view.
When you define a variable, you must provide both name and RMC name.
|Name||Title to display against the headline on the view.|
RMC name identifying the source managed variable.
For more information, see $HOST and $INSTANCE substitutions.
Provides the option to show the variable as a rate.
When Show as rate is enabled, then you can configure the following options:
For more information on the Show as rate options, see Rate calculation.
When you create a data template, you can choose from two approaches:
The records option constructs a list of variables in the view. This option should be used when the variable names are known at the time the template is created.
The records section is similar to the headlines section, except the variables are displayed in a list and the number of the variables is not limited to six—you can define up to 1000 variables.
The other difference from the headlines section is that records section must be in the template on its own—a template cannot have both a LIST section and a TABLE section.
For more information, see the RMC Interface Records Option.
The table option constructs a table in the view. Use this when the full variable names are not known at the time the template is created.
For example, when monitoring Sink Distributor User Mounts it is not possible to fully specify the variable names, as new mounts may come and go. Instead, a pattern that the variable names fall into is specified.
For more information, see the RMC Interface Table Option.
This option enables you to create a detached table or record, which can be used by more than one RMC Interface sampler.
When you select this option, the RMC Interface sampler defines or attaches itself to an RMC template from static variables. If the template does not exist, then the sampler prompts you to create a new one using the data template options.
For more information on the data template option, see Data template.
When defining fields in the data template, you have the option to show values as rates.
Some RMC variables contain counters that are incremented since the RMDS component is started; for example, the total messages received. In itself, this number is not useful; however, the rate of change of this number is a useful parameter to monitor:
Signed wrap— monitors for signed wrap-around in the value of the variable being monitored.
Unsigned wrap— monitors for unsigned wrap-around in the value of the variable being monitored.
Change between samples— calculates the rate based on the difference between the current value and the value when the previous sample occurred. This means that the rate is calculated based on the current and the last sampled value, which could be the same value.
Change between syncs— the default method used when no method is explicitly set in the configuration. This method exhibits the gradually declining rate, as it calculates the rate based on the difference between the current value and the last value received into the data store from a sync. This means that the rate is calculated based on the current value and the last value read and stored by the plug-in not equal to the current value. The gradually declining rate is expected.
When dealing with mounts, this option enables the RMC Interface sampler to translate an application ID to a name string.
The name string that shows on the dataview for a given application ID.
Names must not have spaces or delimiters.
|Key||The application ID which you want to appear as a name string.|
Name and location of the download template. The interface file is automatically created when you configure the RMC Interface sampler.
Amount of time, in milliseconds, to spend processing incoming data in main thread.
Use this option to tie the detection to a single named process instance.
Name of the actual publishing process that writes to the shared memory. If this is set then the plug-in will verify that the process is up to validate the shared memory state.
|Args||Arguments passed to the actual publishing process. This helps to identity the process - e.g -install .gw|
For more information, see Shared Memory Status Detection.
shmget() shared memory tests within the RMC plug-in. This is enabled by default. When disabled, the plug-in proceeds with monitoring without checking the shared memory status. Disable only when diagnosing syncing issues between the plug-in and the RMC component/s being monitored.
|Use timing record||Enables shared memory status detection method using time statistics read from the shared memory. This can be used together with the default shared memory status test.|
Time out value in seconds.
Default value: 15
|Variable name||Name of the variable that contains the timing record from the shared memory statistics.|
For more information, see Shared Memory Status Detection.
RMC variable names can include
$instance. In this case, the
$host is replaced with
the hostname of the machine the plug-in is running on
$instance is replaced with the INSTANCE variable
For troubleshooting purposes and to get a simpler overview of the content of the shared memory, you can use the rmc recorder tool. This can be downloaded from the utilities section.
./rmcRecorder.linux_64 -k 80
This can also be piped into a file using
-k indicated that we are querying shared memory key 80 (standard ADH)