RTI Connext C API Version 7.3.0
|
This data structure is used to configure event and periodic metrics collection and distribution for a specific set of observable resources. More...
Data Fields | |
char * | resource_selection |
An expression pattern that selects a subset of resources by matching the pattern to the resource names. DDS_MonitoringMetricSelection::enabled_metrics_selection and DDS_MonitoringMetricSelection::disabled_metrics_selection are applied to this subset of resources. More... | |
struct DDS_StringSeq | enabled_metrics_selection |
A sequence of POSIX fnmatch patterns that match the names of the metrics that should be collected and distributed for the observable resources selected by DDS_MonitoringMetricSelection::resource_selection. More... | |
struct DDS_StringSeq | disabled_metrics_selection |
A sequence of POSIX fnmatch patterns that mach the names of the metrics that should not be collected and distributed for the observable resources selected by DDS_MonitoringMetricSelection::resource_selection. More... | |
This data structure is used to configure event and periodic metrics collection and distribution for a specific set of observable resources.
char* DDS_MonitoringMetricSelection::resource_selection |
An expression pattern that selects a subset of resources by matching the pattern to the resource names. DDS_MonitoringMetricSelection::enabled_metrics_selection and DDS_MonitoringMetricSelection::disabled_metrics_selection are applied to this subset of resources.
Examples of resource expression patterns:
The first expression refers to a DomainParticipant named "myParticipant" that belongs to an application named "myApp". The second expression applies to all the Subscribers in the system (resource name wildcards follow the POSIX fnmatch syntax). The third expression refers to a DomainParticipant with a specific resource GUID in the "myApp" application. The last expression uses the XPath "//" operator. It matches observable resources named "myEntity" no matter where they are located in the resource hieararchy.
See the Telemetry Data / Resources chapter of the RTI Connext Observability Framework documentation for further information on the observable resource names and expression patterns.
struct DDS_StringSeq DDS_MonitoringMetricSelection::enabled_metrics_selection |
A sequence of POSIX fnmatch patterns that match the names of the metrics that should be collected and distributed for the observable resources selected by DDS_MonitoringMetricSelection::resource_selection.
This sequence is evaluated first, followed by DDS_MonitoringMetricSelection::disabled_metrics_selection. Therefore, if the same metric is enabled and disabled at the same time, the disablement will be the final result.
The patterns in the sequence are evaluated in order.
Examples of valid patterns:
The first pattern refers to a specific DataWriter metric (DDS_DurabilityQosPolicy::writer_depth). The second pattern refers to all the DataReader DDS_ReliabilityQosPolicy metrics. The last pattern selects all the available application metrics.
See the Telemetry Data / Metrics chapter of the RTI Connext Observability Framework documentation for further information on the metric names and metric patterns.
struct DDS_StringSeq DDS_MonitoringMetricSelection::disabled_metrics_selection |
A sequence of POSIX fnmatch patterns that mach the names of the metrics that should not be collected and distributed for the observable resources selected by DDS_MonitoringMetricSelection::resource_selection.
This sequence is evaluated after DDS_MonitoringMetricSelection::enabled_metrics_selection. Therefore, if the same metric is enabled and disabled at the same time, the disablement will be the final result.
The patterns in the sequence are evaluated in order.
Examples of valid patterns:
The first pattern refers to a specific DataWriter metric (DDS_DurabilityQosPolicy::writer_depth). The second pattern refers to all the DataReader DDS_ReliabilityQosPolicy metrics. The last pattern selects all the available application metrics.
See the Telemetry Data / Metrics chapter of the RTI Connext Observability Framework documentation for further information on the metric names and metric patterns.