40. Using Monitoring Library in Your Application

40.1 Enabling Monitoring

There are two ways to enable monitoring in your application:

• 40.1.1 Method 1—Change the Participant QoS to Automatically Load the Dynamic Monitoring Library
• 40.1.2 Method 2—Change the Participant QoS to Specify the Monitoring Library Create Function Pointer and Explicitly Load the Monitoring Library

Notes:

• The libraries that you will need for Monitoring are listed in the RTI Connext DDS Core Libraries Platform Notes.
• If your original application has made modifications to the ParticipantQos resource_limits.type_code_max_serialized_length, ParticipantQos resource_limits.type_object_max_serialized_length, or any of the transport's default settings to enable large type code or large data, refer to 40.3 What Monitoring Topics are Published? for additional QoS modifications that may be needed.
• Monitoring Library creates internal DataWriters to publish monitoring data by making modifications based on the default DataWriter QoS settings. If you have made changes to the default DataWriter QoS, especially if you have increased/decreased the initial or maximum DDS sample/instance values, Monitoring Library may have trouble creating DataWriters to publish monitoring data, or it may limit the number of statistics that you can publish through the internal monitoring writers. If this is true for your case, you may want to specify the qos_library and qos_profile that will be used to create these internal writers for publishing monitoring data, to avoid being impacted by default DataWriter QoS settings. See 41. Configuring Monitoring Library for details.

© 2020 RTI