6.2. Resources
Observability Library collects telemetry data associated with observable resources. In this release, the observable resources are:
Application (one-to-one mapping to an OS process)
Participant
Topic
Publisher
Subscriber
DataWriter
DataReader
Each observable resource is identified by a GUID and a resource name. The
GUID is automatically assigned by Observability Library, and it is
globally unique across all the resources in the system (past and present).
The resource GUID can be accessed using the guid
label
associated with each metric. See Metrics for
detailed information about the metrics available in this release.
Table 6.1 lists details of each available resource. The resource names follow REST best practices for naming.
Resource |
Resource Name |
Dashboard Resource Name |
How to Configure |
---|---|---|---|
Application |
|
|
To set <AppName>, configure the
|
Participant |
|
|
To set <ParticipantName>, configure the
|
Topic |
|
|
<TopicName> is the name of the DDS Topic. This resource cannot be configured in the Monitoring QoS. |
Publisher |
|
Dashboards do not show information about Publishers |
To set <PublisherName>, configure the
|
Subscriber |
|
Dashboards do not show information about Subscribers |
To set <SubscriberName>, configure the
|
DataWriter |
|
|
To set <DataWriterName>, configure the
|
DataReader |
|
|
To set <DataReaderName>, configure the
|
The Dashboard Resource Name column describes how resource names appear in RTI Connext Observability Dashboards. To generate shorter names, Observability Dashboards does not show the resource class name (e.g, domain_participants).
Important
Observability Framework does not enforce unique resource names. You are responsible for assigning unique names. When two observable resources have the same name, the commands targeting the resource name are applied to both resources. For example, if two applications have the same name and you change the logging verbosity from Observability Dashboards, the change will apply to both applications. Otherwise, not having unique names should not affect functionality because each resource has a unique GUID.