13.5. What’s New in 7.6.0

This section describes what’s new in Observability Framework 7.6.0 compared to release 7.5.0.

RTI® Connext® 7.6.0 is an early access release. See the Connext Versions and Lifecycle page for more information on RTI’s software release model.

For what’s new and fixed in other products in the Connext suite, see those products’ release notes on the RTI Community Portal or in your installation.

13.5.1. Implemented scalable remote system debugging

Collector Service now supports retrieving telemetry data through a chain of Collector Service instances. Edge Collector Service instances can collect and forward telemetry to a centralized Collector Service instance. This improvement makes it possible to monitor and debug large, distributed systems spanning multiple networks.

For more information, see Collector Service.

13.5.2. More flexibility when configuring Collector Service for remote debugging

Collector Service includes additional built-in configuration profiles for use when collecting telemetry data from remote systems.

NonSecureRemoteDebuggingWAN to collect remote debug data from a remote system without security.
SecureRemoteDebuggingLAN to collect remote debug data from a local system using RTI security features.

In addition, two existing profiles were renamed to follow the established naming convention:

SecureRemoteDebugging → SecureRemoteDebuggingWAN
NonSecureRemoteDebugging → NonSecureRemoteDebuggingLAN

For more information, see Remote Debugging in the Admin Console User’s Manual.

13.5.3. New built-in profile makes it easier to monitor Connext applications across geographically separated networks

This release introduces a new built-in profile called BuiltinQosLib::Generic.Monitoring2.WAN, which allows connecting to a Collector Service instance over the WAN using the RTI Real-Time WAN Transport. Connecting over the WAN enables you to use Observability Framework to monitor and collect telemetry data from Connext applications that are distributed across geographically separated networks, even when they are behind NATs. The new profile makes it easier to set up the connection over the WAN.

For example:

<qos_library name="MyQosLibrary">
     <qos_profile name="MyApplicationProfile" is_default_participant_factory_profile="true">
         <participant_factory_qos>
             <monitoring>
                 <enable>true</enable>
                 <distribution_settings>
                     <dedicated_participant>
                         <collector_initial_peers>
                             <element>udpv4_wan://38.21.45.34:4500</element>
                         </collector_initial_peers>
                         <participant_qos_profile_name>
                             BuiltinQosLib::Generic.Monitoring2.WAN
                         </participant_qos_profile_name>
                     </dedicated_participant>
                 </distribution_settings>
             </monitoring>
         </participant_factory_qos>
     </qos_profile>
 </qos_library>

For additional information, see Connecting to Collector Service Over WAN.

13.5.4. Decreased bandwidth usage when not actively debugging remote systems

Previously when using the Remote Debugging feature in Admin Console, Monitoring Library 2.0 sent all telemetry data generated by a Connext application to Collector Service. Now, telemetry data is sent only if an active Admin Console session requests the data, reducing unnecessary network traffic and improving system efficiency.

See Remote Debugging in the RTI Admin Console User’s Manual, for more information.

13.5.5. Third-Party Software Changes

The following third-party software used by Observability Framework has been upgraded:

Table 13.2 Third-Party Software Upgrades
Third-Party Software	Old Version	New Version
OpenSSL	3.0.12	3.5.1

In addition to the upgrade, the OpenSSL target packages for armv8Linux4gcc7.3.0, QNX, and Android now include assembly implementations for cryptographic operations (the packages were built using the asm_arch and perlasm_scheme options described in this OpenSSL README file). This change affects only the libcrypto and libssl libraries; the openssl executable is still configured with no-asm.

For information on third-party software used by Connext products, see the “3rdPartySoftware” documents in your installation: <NDDSHOME>/doc/manuals/connext_dds_professional/release_notes_3rdparty.