<<extension>> Configures the use of a dedicated DDS_DomainParticipant to distribute the RTI Connext application telemetry data. More...

Data Fields
DDS_Boolean	enable
	<<basic>> <<extension>> Enables the use of a dedicated DDS_DomainParticipant to distribute the RTI Connext application telemetry data. More...

int	domain_id
	<<basic>> <<extension>> The domain ID used in the creation of RTI Monitoring Library 2.0 DDS_DomainParticipant. More...

char *	participant_qos_profile_name
	<<extension>> The fully qualified name of the profile used to configure the DDS_DomainParticipant that will be used to distribute telemetry data. More...

struct DDS_StringSeq	collector_initial_peers
	<<basic>> <<extension>> Determines the initial list of peers that the discovery process will contact to send announcements about the presence of the DDS_MonitoringDistributionSettings::dedicated_participant. More...

Detailed Description

<<extension>> Configures the use of a dedicated DDS_DomainParticipant to distribute the RTI Connext application telemetry data.

Field Documentation

◆ enable

DDS_Boolean DDS_MonitoringDedicatedParticipantSettings::enable

<<basic>> <<extension>> Enables the use of a dedicated DDS_DomainParticipant to distribute the RTI Connext application telemetry data.

Setting this value to DDS_BOOLEAN_FALSE is not currently supported.

[default] DDS_BOOLEAN_TRUE

Categories: Mutable, Debuggability, QoS Profile Management

◆ domain_id

int DDS_MonitoringDedicatedParticipantSettings::domain_id

<<basic>> <<extension>> The domain ID used in the creation of RTI Monitoring Library 2.0 DDS_DomainParticipant.

By default, the RTI Monitoring Library 2.0 DomainParticipant is created in domain 101 with the domain tag 'RTI_o11y'. The domain tag provides further isolation in case the application also uses domain 101.

The domain ID can be changed using this field. Changing the domain tag is not recommended. However, if you need to change it, you must do so by configuring the domain tag in the DDS_DomainParticipantQos of the profile set in DDS_MonitoringDedicatedParticipantSettings::participant_qos_profile_name.

[default] 101

Categories: Mutable, Debuggability, Discovery, Discovery Isolation

◆ participant_qos_profile_name

char* DDS_MonitoringDedicatedParticipantSettings::participant_qos_profile_name

<<extension>> The fully qualified name of the profile used to configure the DDS_DomainParticipant that will be used to distribute telemetry data.

If NULL (the default value) then RTI Monitoring Library 2.0 uses DDS_PROFILE_GENERIC_MONITORING2.

[default] NULL

Categories: Mutable, Debuggability, QoS Profile Management

◆ collector_initial_peers

struct DDS_StringSeq DDS_MonitoringDedicatedParticipantSettings::collector_initial_peers

<<basic>> <<extension>> Determines the initial list of peers that the discovery process will contact to send announcements about the presence of the DDS_MonitoringDistributionSettings::dedicated_participant.

These initial peers should correspond with the RTI Observability Collector Service with which RTI Monitoring Library 2.0 has to communicate. The collector_initial_peers works the same as initial_peers for other DomainParticipants, except that it allows you to easily specify the initial peer(s) for the RTI Monitoring Library 2.0 DDS_DomainParticipant, which may have different initial peer(s) than those used by your application.

If no collector_initial_peers are specified, or if it is explicitly set to an empty list, the DDS_DiscoveryQosPolicy::initial_peers list of DDS_MonitoringDedicatedParticipantSettings::participant_qos_profile_name will be used as the initial peers of DDS_MonitoringDistributionSettings::dedicated_participant.

[default] An empty sequence.

See also: DDS_DiscoveryQosPolicy::initial_peers for further information about initial peers.