2.2.4. RTI Connext Observability Framework

Observability Framework in release 7.5.0 works with Connext 7.3.0 and 7.5.0. See the Observability Framework Release Notes 7.5.0 for more information on Observability Framework in 7.5.0.

2.2.4.1. Optionally disable distribution and collection of remote debugging data

In 7.5.0, enabling Monitoring Library 2.0 using the BuiltinQosSnippetLib::Feature.Monitoring2.Enable Qos snippet or manually with the wild card * in the <enable_metrics_selection> not only collects telemetry data, but data that RTI Admin Console uses for its new remote debugging feature. Collecting and distributing this extra data doesn’t do any harm; however, it puts more data on the wire that Observability Framework doesn’t use.

If you want to stop the distribution and collection of remote debugging data in this release, add a <disabled_metrics_selection> section to your Monitoring Library 2.0 configuration as shown in the example below. In the example, your configuration has enabled all <resource_selection> metrics. To disable the remote debugging data, add the <disabled_metrics_selection> lines as shown below. The *_rti_sentinel value disables the collection and distribution of all Admin Console remote debugging information.

Note

If you intend to run both Observability Framework and the RTI Admin Console remote debugging feature, then do not disable the remote debugging data as shown in the example below.

 <qos_library name="MyQosLibrary">
     <qos_profile name="MyApplicationProfile" is_default_participant_factory_profile="true">
         <participant_factory_qos>
             <monitoring>
                 <!-- Enable monitoring -->
                 <enable>true</enable>
                 <!-- Enable all metrics -->
                 <telemetry_data>
                     <metrics>
                         <element>
                             <resource_selection>//*</resource_selection>
                             <enabled_metrics_selection>
                                 <element>*</element>
                             </enabled_metrics_selection>
                             <disabled_metrics_selection>
                                 <element>*_rti_sentinel</element>
                             </disabled_metrics_selection>
                         </element>
                     </metrics>
                 </telemetry_data>
                 <!-- Change the application name -->
                 <application_name>MyApplication</application_name>
                 <distribution_settings>
                     <dedicated_participant>
                         <!-- Change the Observability Domain ID -->
                         <domain_id>7</domain_id>
                         <!-- Change the initial peers of the
                              Observability DomainParticipant -->
                         <collector_initial_peers>
                             <element>192.168.1.2</element>
                         </collector_initial_peers>
                     </dedicated_participant>
                 </distribution_settings>
             </monitoring>
         </participant_factory_qos>
     </qos_profile>
 </qos_library>

If you have enabled metrics globally, you only need to disable the remote debugging data once as shown in the above example; if you have enabled metrics at entity levels (as shown in Configuring QoS for Monitoring Library 2.0 Entities in the Observability Framework documentation), you may need to disable the remote debugging data at each level.

Monitoring Library 2.0’s BuiltinQosSnippetLib::Feature.Monitoring2.Enable snippet enabling the collection and distribution of remote debugging data will be fixed in an upcoming release.