Changes in this Release

This preface lists changes in the Oracle Autonomous Health Framework Checks and Diagnostics User's Guide 25.5.

Upgrade Configuration Management

Starting with release 25.5, the AHF commands for managing upgrade configurations have been replaced with new SDK CLI commands.

You are encouraged to transition to the new SDK CLI commands, as the existing ahfctl commands will be deprecated and be removed in a future release.

The legacy ahfctl command line, which is also slated for deprecation, currently provides the following commands for managing AHF upgrades:
The following new commands are implemented within the ahf configuration command category, offering a simplified way to manage AHF upgrade configurations. However, to ensure compatibility with future releases and to benefit from enhanced functionality, you must adopt the new SDK CLI commands for upgrade management.
  • To set AHF upgrade configuration parameters, run:
    ahf configuration set --type upgrade [--software-stage SOFTWARE_STAGE] [--auto-upgrade AUTO_UPGRADE] [--upgrade-time UPGRADE_TIME][--file-system-type FILE_SYSTEM_TYPE] [–temporary-location TEMPORARY_LOCATION] [--remove-installer REMOVE_INSTALLER] [–frequency FREQUENCY] [--service-name SERVICE_NAME] [--auto-update AUTO_UPDATE]
  • To get AHF upgrade configuration parameter details, run:
    ahf configuration get --type upgrade [--to-json TO_JSON]
  • To unset AHF upgrade configuration parameters, run:
    ahf configuration unset --type upgrade [--software-stage SOFTWARE_STAGE] [--auto-upgrade AUTO_UPGRADE] [--upgrade-time UPGRADE_TIME][--file-system-type FILE_SYSTEM_TYPE] [–temporary-location TEMPORARY_LOCATION] [--remove-installer REMOVE_INSTALLER] [–frequency FREQUENCY] [--service-name SERVICE_NAME] [--auto-update AUTO_UPDATE]

Related Topics

Parent topic: Changes in this Release

Optimized Data Upload to AHF Fleet Insights

Starting with release 25.5, the data uploaded from AHF to AHF Fleet Insights has been optimized to reduce payload size.

A data optimization process has been implemented to reduce payload size and improve data processing speed. Uploading only essential data enhances the user experience by delivering the most critical and up-to-date insights.

Parent topic: Changes in this Release

Audit Event for Oracle Trace File Analyzer (TFA) Opt-In Changes

In cloud environments, an audit event will now be sent to the support team whenever there is a change to any TFA opt-in variable.

The following TFA opt-in variables can be set by the user to on or off:
  • customerDiagnosticsNotifications
  • cloudOpsLogCollection
  • cloudOpsHealthMonitoring

These variables control whether telemetry information is sent to the support team and/or the customer. Customers often raise SRs when expected metrics are missing from their dashboards.

During triage, the support team typically requests the current values of these variables to determine whether a misconfiguration is preventing telemetry data from being sent. With this enhancement, TFA automatically sends an event to the support team every time the state of any of the above variables changes.

Benefits:
  • Faster triage response times: Support is immediately notified when a customer opts out.
  • Improved stability: Opt-in changes no longer restart the Telemetry Adapter process, reducing load on OCI services and preventing potential data loss.

Parent topic: Changes in this Release

ProcessCountSpike Signature Included in Oracle Orachk Report

Starting with release 25.5, the ProcessCountSpike signature is included in the Cluster Health Monitor (CHM) Analysis section of the Oracle Orachk report.

A spike in the number of processes can severely impact system performance. Excessive processes may exhaust available memory resources, potentially leading to system instability, crashes, or unresponsiveness. Furthermore, increased process contention for shared resources can introduce performance bottlenecks and conflicts. The ProcessCountSpike signature helps detect such conditions and is included as part of the Cluster Health Monitor (CHM) Analysis report in Oracle Orachk.

Figure -1 Process Spike Count Signature - Oracle Orachk report


This image illustrates the Process Spike Count Signatture section in the Oracle Orachk report.

Parent topic: Changes in this Release

Process Start Time and Cumulative CPU Time in Top Resource Consuming Process Stats Included in Oracle Orachk and AHF Insights Reports

This enhancement provides process start time and cumulative CPU time for the top resource-consuming processes, based on I/O, CPU, and RSS usage.

  • Process Start Time indicates the exact date and time a process began executing on the system.
  • Cumulative CPU Time represents the total amount of CPU time consumed by a process since it started.

These metrics are especially valuable when analyzing customer Service Requests (SRs). Knowing when a top resource-consuming process started enables better correlation with incidents and system events, thereby improving debugging and troubleshooting efforts.

Additionally, cumulative CPU time helps identify long-running or CPU-intensive processes that could be causing performance bottlenecks.

How can process stats be accessed in Oracle Orachk and AHF Insights reports?

Process statistics in Oracle Orachk and AHF Insights reports can be accessed under the Top CPU Consuming Processes section. Two key columns provide improved visibility into top I/O-consuming processes:
  • StartTime: Shows the process start time.
  • TIME+(MM:SS.ms): Displays the cumulative CPU time.

These column names align with those used in standard operating system commands like top and ps, offering a familiar reference for interpreting system-level process data.

Figure -2 Process Start Time and Cumulative CPU Time in Top Resource Consuming Process Stats - Oracle Orachk report


This image illustrates Process Start Time and Cumulative CPU Time in Top Resource Consuming Process Stats in Oracle Orachk report.

Figure -3 Process Start Time and Cumulative CPU Time in Top Resource Consuming Process Stats - AHF Insights report


This image illustrates Process Start Time and Cumulative CPU Time in Top Resource Consuming Process Stats in AHF Insights report.

Parent topic: Changes in this Release

Aggregation of Processes by Name Prefix Included in Oracle Orachk Report

This feature categorizes processes based on their name prefixes and displays the count of processes within each category.

In many cases, memory issues are not caused by a single large process, but rather by a group of similar processes that collectively consume significant memory. These grouped processes may not appear among the top memory consumers individually, nor may they be detected through simple memory usage comparisons across two time ranges.

By aggregating processes using their name prefixes, this feature provides better visibility into the total number of such processes running on the system.

This enhancement has been incorporated into the inline diff report under the AvailableMemoryLow signature, enabling users to identify patterns of grouped process behavior that might otherwise go unnoticed.

Figure -4 Aggregation of Processes by Name Prefix - Oracle Orachk report


This image illustrates Aggregation of Processes by Name Prefix in Oracle Orachk report

Figure -5 Aggregation of Processes by Name Prefix - Diff report


This image illustrates Aggregation of Processes by Name Prefix diff report

Parent topic: Changes in this Release

New Oracle Orachk and Oracle Exachk Best Practice Checks

Release 25.5 includes the following new Oracle Orachk and Oracle Exachk best practice checks.

Oracle Orachk Specific Best Practice Checks

  • Verify ASM Filter Driver (AFD) configuration

All checks can be explored in more detail via the Health Check Catalogs:

Related Topics

Parent topic: Changes in this Release