Resolving JMS Plug-in Health Issues

Issue 1: The JMS plugin in the instance cannot register with JMS Fleets due to a missing policy.

Resolution Options:

Option 1: Review your policy to verify group definitions, resource type, or compartment in the policy statements. Ensure that your policy includes the following policy statement:
ALLOW DYNAMIC-GROUP JMS_DYNAMIC_GROUP TO MANAGE log-content IN COMPARTMENT $(compartmentName)
where $(compartmentName) is the compartment to which the fleet belongs.

Option 2: If the instance is an Oracle Linux OCI monitored using Oracle Cloud Agent, disable the JMS plug-in from the Oracle Cloud Agent tab if it was enabled by mistake or is no longer needed. Disabling the JMS plug-in means that the instance will not be monitored by any JMS fleet.

Issue 2: The JMS plugin in the instance encountered errors while trying to push inventory data to the fleet inventory or operational logs, probably due to missing policies.

Resolution Options:

Option 1: Review your policy to verify group definitions, resource type, or compartment in the policy statements. Ensure that your policy includes the following policy statement:
ALLOW DYNAMIC-GROUP JMS_DYNAMIC_GROUP TO MANAGE log-content IN COMPARTMENT $(compartmentName)
where $(compartmentName) is the compartment to which the fleet belongs.

Option 2: If the instance is an Oracle Linux OCI monitored using Oracle Cloud Agent, disable the JMS plug-in from the Oracle Cloud Agent tab if it was enabled by mistake or is no longer needed. Disabling the JMS plug-in means that the instance will not be monitored by any JMS fleet.

Issue 3: The JMS plugin in the instance is not associated with any fleet. This may happen if the plugin is enabled under OCA but registration is not completed.

Resolution Options:

Option 1: Complete the registration of the JMS plug-in to the fleet. Use the Add Managed Instance(s) action in the Managed instance(s) table of the fleet.
  1. Go the fleets listing page.
  2. Choose the fleet with which you want to associate the instance.
  3. Navigate to the managed instances resource within the Fleet details page.
  4. Click Add managed instance and locate this instance.
  5. Complete the registration process.

Option 2: If the instance is an Oracle Linux OCI monitored using Oracle Cloud Agent, disable the plug-in from the Oracle Cloud Agent tab if it was enabled by mistake or is no longer needed. Disabling the JMS plug-in means that the instance will not be monitored by any JMS fleet.