13.6.1. What’s New in 7.2.0

13.6.1.1. Observability Collector Service compatible with Monitoring Library 2.0

All the DomainParticipants from Collector Service are correctly detected using Monitoring Library 2.0 and Observability Framework.

To activate Monitoring Library 2.0 in Collector Service, run the service from a folder with a file named USER_QOS_PROFILES.xml and the following content:

<?xml version="1.0"?>
<dds>
    <qos_library name="MonitoringEnabledLibrary">
        <qos_profile name="MonitoringEnabledProfile" is_default_participant_factory_profile="true">
            <participant_factory_qos>
                <monitoring>
                    <enable>true</enable>
                </monitoring>
            </participant_factory_qos>
        </qos_profile>
    </qos_library>
</dds>

For more information about using XML QoS profiles, see How to Load XML-Specified QoS Settings, in the RTI Connext Core Libraries User’s Manual

13.6.1.2. Support for most observability backends with OpenTelemetry integration

Previously, Observability Framework only allowed storing metrics in a Prometheus time-series database and logs in a Grafana Loki log aggregator. This release adds support for sending telemetry data (metrics and logs) to an OpenTelemetry Collector, providing a way to store the telemetry data in other third-party observability backends.

13.6.1.3. Support for Observability Collector Service security

Starting with RTI Connext 7.2.0, Collector Service can be secured using the Security Plugins to communicate with Monitoring Library 2.0. (see Secured communications between Monitoring Library 2.0 and Observability Collector Service). Collector Service can also use BASIC-Auth over HTTPS to secure the telemetry data sent to the observability backends and the remote commands received from Observability Dashboards.

For additional details, see Support for RTI Observability Framework in the RTI Security Plugins User’s Manual.

13.6.1.4. Name change from “RTI Observability Library” to “RTI Monitoring Library 2.0”

For details, see RTI Connext Core Libraries What’s New in 7.2.0.

13.6.1.5. Name change for some Observability metrics

This release changes the name of some metrics associated with Connext entities.

This change applies to the following eight metrics. See the Metrics section of this user manual for details about all available metrics.

Table 13.4 Metric Name Changes
Old Metric Name	New Metric Name
`dds_application_process_utilization_memory_usage_resident_memory_bytes`	`dds_application_process_memory_usage_resident_memory_bytes`
`dds_application_process_utilization_memory_usage_virtual_memory_bytes`	`dds_application_process_memory_usage_virtual_memory_bytes`
`dds_datawriter_reliable_cache_unacknowledged_samples`	`dds_datawriter_reliable_cache_unack_samples`
`dds_datawriter_reliable_cache_unacknowledged_samples_peak`	`dds_datawriter_reliable_cache_unack_samples_peak`
`dds_datawriter_reliable_cache_replaced_unacknowledged_samples_total`	`dds_datawriter_reliable_cache_replaced_unack_samples_total`
`dds_datareader_cache_old_source_timestamp_dropped_samples_total`	`dds_datareader_cache_old_source_ts_dropped_samples_total`
`dds_datareader_cache_tolerance_source_timestamp_dropped_samples_total`	`dds_datareader_cache_tolerance_source_ts_dropped_samples_total`
`dds_datareader_cache_samples_dropped_by_instance_replacement_total`	`dds_datareader_cache_samples_dropped_by_instance_replaced_total`

13.6.1.6. Secured communications between Monitoring Library 2.0 and Observability Collector Service

For details, see RTI Security Plugins What’s New in 7.2.0.

13.6.1.7. Ability to set initial forwarding verbosity in MONITORING QoS policy

For details, see RTI Connext Core Libraries What’s New in 7.2.0.

13.6.1.8. Ability to set collector initial peers in MONITORING QoS policy

For details, see RTI Connext Core Libraries What’s New in 7.2.0.

13.6.1.9. Third-Party software changes

13.6.1.9.1. Observability Framework

The following third-party software is now used by the scripts that configure Observability Framework:

Table 13.5 Observability Framework Third-Party Software Changes
Third-Party Software	Version
bcrypt	4.0.1
Jinja2	3.0.0

13.6.1.9.2. Observability Collector Service

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

Table 13.6 Collector Service Third-Party Software Upgrades
Third-Party Software	Previous Version	Current Version
CivetWeb	1.15	1.16
OpenTelemetry C++	1.4.1	1.9.1

13.6.1.9.3. Docker containers for Observability Collector Service

The following third-party software is now used by the Docker containers created by Observability Framework:

Table 13.7 Third-Party Software Changes (Docker Containers)
Third-Party Software	Version
NGINX	1.24.0
OpenTelemetry Collector	0.80.0

The following third-party software used by the Docker containers created by Observability Framework have been upgraded:

Table 13.8 Third-Party Software Upgrades (Docker Containers)
Third-Party Software	Previous Version	Current Version
Prometheus	2.37.5	2.37.8
Grafana	9.2.1	9.5.3
Grafana Loki	2.7.0	2.8.2

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.

Warning

All third-party software is subject to third-party license terms and conditions. IT IS YOUR RESPONSIBILITY TO ENSURE THAT YOUR USE OF THIRD-PARTY SOFTWARE COMPLIES WITH THE CORRESPONDING THIRD-PARTY LICENSE TERMS AND CONDITIONS.