The Monitor Service targets any application implementing the subscription side of the Monitor Service Status Topic <monitor_service_topics>, giving the possibility of retrieving the Monitoring Information <monitor_service_keywords> of the local entities (incompatible QoS, deadlines missed, active connections,...).
- Proxy: An entity that acts on behalf of another entity.
- Proxy Data: The way in which a Proxy can be described.
- Monitoring Information: The collection of different sources of information and statuses of an entity, including: the Proxy Data, incompatible QoS, connections, liveliness, deadlines missed, inconsistent topics and lost sample status.
Enabling the service makes each publish its local entities, each one with its related Monitoring Information.
The monitor_service is disabled by default, as it may entail a performance cost. Further information on the monitor_service topics and how to configure it is described in the following sections.
The monitor_service is available in both the DDS Layer <dds_layer> and RTPS Layer <rtps_layer>.
Note
If the service is activated within a RTPS <rtps_layer> context, not all the Monitoring Information may be published by the service.
The monitor_service can be particularly useful in the following scenarios:
- Collecting the
Monitoring Informationof any local entity of a remote in order to extend the default discovery information (seediscovery) about it. - Troubleshooting issues regarding discovery or entity-matching, leveraging the information of the current locators in use, for example.
- Recreating an entity graph of a certain domain given that all participants are able to discover each other.