Managed Instances
Click Managed instances to view the table of managed instances for the selected fleet. The table presents a list of managed instances that have reported the presence of a Java installation or the start of a Java application.
In the Search and Filter text field, you can filter the displayed resources by using the drop-down menu. The available options include:
- Search by host: filter the list of managed instances by host name
- Operating system: filter the list of managed instances by your required operating system
You can customize the table columns by using the Manage columns icon.
Use Applied filters drop-down to select the required time period for displaying the resources. By default, resources pertaining to last 7 days are displayed.
- Host: name of the host associated with the managed instance
- Agent status: status of the agent
- Initializing: the agent has registered with JMS, but it's in a transitory state until it is fully functional. An agent can remain in this state up to 15 minutes, and if this state persists, this could imply a communication error between the agent and the agent service.
- Active: the agent service is communicating with the agent, and the agent is functioning as expected.
- Silent: the agent service isn't communicating with the agent. While communication was established after the agent installation, there currently might be a communication problem between the agent service and the agent.
- Deleted: the management agent or the compute instance have been deleted or the agent has been deleted from the Java Management service console. In the latter case, the agent might be running but isn't functional because it isn't attached to any fleet.
- Moved: the agent has been moved to another fleet.
- Unregistered: an agent that was associated to a fleet but was detached due to lack of activity.
- Needs Attention: the agent is not functioning properly or is misconfigured.
- Agent security state: specifies the agent security state, such as Update available
- OCID: OCIDs of the managed instances in the fleet that have Java installation or Java application started at the selected time period
- Java runtime installations: number of Java applications installed on the managed instance at the selected time period
- Applications: number of applications installed on the host at the selected time period
- Deployed applications: number of application deployed on the Java server at the selected time period
- Operating system: operating system of the host, such as Windows, Linux
- First reported: date and time when the managed instance was first reported
- Last reported: date and time when the managed instance was last reported
For more information about a managed instance, see Managed Instance.
You can also perform the following actions on the managed instances:
- Add unregistered managed instances to the fleet. See Add Managed Instance(s)
- Move one or more managed instances to another fleet. See Move Managed Instances.
- Remove one or more managed instances from the fleet. See Remove Managed Instance
- Install the required version of Java runtime. See Install a Java Runtime.
- View the DRS settings. See Manage Deployment Rule Set
- Perform event analysis to understand the usage of JDK in your fleets. See Crypto Event Analysis.
- Initiate scan for Java servers in one or more managed instances. See Scan for Java Servers.
- Initiate scan for Java libraries in one or more managed instances. See Scan for Java Libraries.
Select the required managed instance and use horizontal ellipsis (…) to Copy OCID.
In the Items per page field, choose 10, 20, 50, or 100 items to display. Select the header of a column to sort the list based on the title of the column.
Click the host name of a managed instance to view its details. See Managed Instance Details.