The OCID of the Management Agent (OMA) or the Oracle Cloud Agent (OCA) instance where the JMS plugin is deployed.
The agent type.
The availability status.
The OMA/OCA agent's compartment OCID.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}. (See Understanding Free-form Tags).
The OCID of the fleet.
Simple key-value pair that is applied without any predefined name, type, or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}. (See Managing Tags and Tag Namespaces.)
The hostname of the agent.
The OCID to identify this JmsPlugin.
The lifecycle state.
The architecture of the operating system of the plugin.
The distribution of the operating system of the plugin.
The operating system family for the plugin.
The version of the plugin.
System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. System tags can be viewed by users, but can only be created by the system.
Example: {@code {\"orcl-cloud\": {\"free-tier-retained\": \"true\"}}}
The date and time the resource was last reported to JMS. This is potentially after the specified time period provided by the filters. For example, a resource can be last reported to JMS before the start of a specified time period, if it is also reported during the time period.
The date and time the plugin was registered.
Information about a JmsPlugin that has been registered.