Oracle Cloud Infrastructure Documentation

Data Storage and Logging in JMS Fleets

JMS Fleets employs a systematic approach to organizing, storing, and managing data to ensure optimal processing and extended analysis. Raw data collected from events sent by the JMS plugin from each managed instance is initially stored in the associated log objects of the fleet to which the managed instance belongs. JMS leverages the OCI Logging service to categorize this data into two main types: Inventory Logs and Operation Logs.
  • Inventory Logs: These Custom Logs store Java Runtime inventory and usage-related information reported from hosts by the JMS plugin. Inventory logs are mandatory for fleets to function effectively.
  • Operation Logs: These Custom Logs capture operations carried out through JMS Fleets. While optional, operation logs complement inventory logs by providing additional operational insights.

If fleets are created through the OCI console, log objects are created by the JMS Fleets in the same compartment as the fleet. If you're creating fleets using the createFleet API, then you'll need to provide as parameters the OCID's of log group and objects to be associated with the fleet. The log object associated with the fleet can be accessed using the Log Configuration Details present in the Fleet Properties Tab.

Both inventory and operation logs are organized under a Log Group, which facilitates advanced analytics through Logging Analytics. By default, these log objects have a retention period of one month. To preserve data indefinitely, you can establish a Connector Hub connection between the log object and an object storage bucket.

Note

Inventory and operation logs will incur storage costs. See the Oracle Cloud Cost Estimator for more details.

Raw data stored in logs is processed, and aggregated data is transferred to the Autonomous Transaction Processing (ATP) database owned by JMS service. JMS retains this aggregated data for up to three years, enabling users to analyze historical trends and gain actionable insights into their Java workloads.

Read the following for more information about logging: