Forum Stats

  • 3,824,981 Users
  • 2,260,447 Discussions


Know what’s running on your Oracle Cloud Infrastructure instances using the OS Management service

The OS Management service streamlines the process of patching your fleet of Oracle Cloud Infrastructure (OCI) compute instances, helping you maintain secure and optimized compute environments for running your application workloads. In our latest update, we go beyond patching with features that auto-discover and monitor the applications that are running on the OCI compute instances. Best of all, this capability is available at no additional cost to Oracle Cloud Infrastructure subscribers.

Let’s see how you can start using it!

Auto-discovery of running applications

OS Management service periodically checks running processes, automatically identifies the type of application to which it belongs, and starts monitoring its state, overall CPU utilization and memory utilization. So, instead of seeing a flat list of process names, a more recognizable list of running applications with their total CPU utilization and memory utilization is visible. The initial set of applications supported are Oracle Database, Oracle Database Listener, WebLogic Server, Oracle HTTP Server, Apache Server, and Tomcat. 

To get visibility into these applications, login to the OCI console, select Compute under the main menu and select a compute instance. Navigate to the OS Management option, and click on the Monitored Resources tab.

This page shows each application’s current state, CPU utilization and memory utilization. In addition to the current utilization values, review the mean values to understand the overall CPU and memory utilization over different time periods. You can use the percentage change values to get insights into how CPU and memory values compare with the same time last week. For example, with steady workloads, you typically see similar values for CPU and memory week after week. Hence, a significantly higher percentage change value could imply higher demand on the application.

You can also select any application and further review its metric history to understand utilization trends over time.

Easy access to top processes

If CPU or memory utilization on a compute instance is high, and these are not from the discovered applications, you can use the Top Processes page to quickly identify the processes that are currently consuming the most CPU or memory. The process ID is provided in case you need to stop any process. At any time, you can get the latest top process data on-demand using a page refresh.  

Monitoring visibility across the compute instances

The Monitored Resources page has a compartment-level view which provides monitoring visibility across all discovered applications running in compute instances within the compartment. It is not necessary to go to each compute instance page to monitor the applications running on that compute instance.

Sort the table by Name to quickly check the state and resource usage of all similar applications (e.g. all WebLogic servers) within the compartment. The CPU or memory columns can be sorted to determine if any application across all compute instances has unusually high CPU or memory utilization.

Alarm when application resource usage is high

All metric data is stored with the OCI Monitoring service enabling you to leverage its alarms and notifications capabilities. For example, you can create an alarm rule to generate an alarm and send email if your WebLogic Server’s CPU utilization is higher than 90% for more than 15 minutes.

Free, easy, and immediate access

Many monitoring systems require installation, configuration, training, and a certain amount of cost. The OS Management service is free for OCI subscribers, is available by default, and can be used with minimal configuration. Anyone who needs to keep their OS instances secure and optimized can get immediate benefit from the OS Management service.

Getting Started

These features are available on all Oracle Linux-based OCI compute instances that are managed by the OS Management service. For information on how to enable these features, refer to the documentation.