Changes in this Release

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

Exploring AHF Insights Reports from the Command Line

The AHF Insights subshell allows you to explore AHF Insights reports directly from your terminal. This feature enables you to quickly review findings without transferring or unzipping report files, streamlining your workflow.

Prerequisites:

  • AHF must be installed on your system.
  • An AHF Insights report must be available locally or on an accessible path.
To open and explore an AHF Insights report, run:
ahf analysis explore –type insights –report <report-path>

This command will launch an interactive subshell where you can easily query and investigate findings from your AHF Insights report.

Figure -1 Interactive subshell


This image illustrates AHF Insights interactive subshell

To view all events detected in your report, run: show events

Figure -2 Show events


This image illustrates AHF Insights command show events

To see a full list of available commands and options, type: help

CHM Inline Analysis

Inline Analysis is a new feature that will automatically execute on all systems where Autonomous Health Framework (AHF) is installed.

Traditionally, the operating system (OS) metrics collected by Cluster Health Monitor (CHM) or System Health Monitor (SHM) are stored directly in the Grid Infrastructure (GI) Base repository. However, this repository is limited in size—250 MB on HAS 19 and 500 MB on MAIN.

On large FASAAS systems, which may run between 30,000 and 40,000 processes, these size limitations mean that CHM OS data can only be retained for a few hours. As a result, the necessary OS data is frequently missing in most Service Requests (SRs), making it challenging to diagnose and resolve issues effectively.

With the CHM Inline Analysis enhancement, instead of preserving large volumes of raw CHM OS data, the system analyzes these OS metrics and stores only the summary analyzed data. The processed analysis files are significantly smaller than the raw data, allowing for several months of data retention within a 100 MB repository quota.

How it works

  • Collection and Analysis:
    • OS metrics are collected by CHM/SHM as usual.
    • Every hour, Oracle Trace File Analyzer (TFA) triggers Inline Analysis which processes the hourly raw chmosdata/shmosdata gzip files.
  • Storage: Only the analyzed results are kept in the AHF home data repository, dramatically reducing space consumption.
  • Execution and Security: Inline Analysis runs as the root user and is configured with specific resource constraints to avoid impact on system performance.

Benefits

  • Extended Retention: Analyzed data can be retained for several months rather than just a few hours.
  • Reduced Storage Footprint: Only 100 MB of repository space is required, even for large systems.
  • Improved Diagnostics: OS data will be available in more SRs, enabling more effective and timely troubleshooting.

Table -1 Feature Comparison: Traditional vs. Inline Analysis

Feature Previous Approach With Inline Analysis
Data Stored Raw CHM OS data Analyzed (summarized) data
Repository Size (typical) 250 MB (HAS 19), 500 MB (MAIN) 100 MB
Data Retention Hours Months
Impact on Diagnostics Data often missing in service requests (SRs) Data available for analysis

Integrating System Health Monitor (SHM) into AHF for Standalone Non-Root Installations

System Health Monitor (SHM) is a tool that collects essential operating system metrics for Oracle Support, especially valuable in diagnosing initial failures such as node evictions when Service Requests (SRs) are logged.

Note:

Presently, SHM is supported only on Linux platforms.

With this enhancement, Autonomous Health Framework (AHF) will integrate SHM data into its diagnostic collections for non-root, standalone environments, that is, Oracle Restart or Single Instance. This enables non-root users to benefit from OS-level insight reports generated from SHM data, particularly focusing on OS-specific diagnostics.

For the initial release (25.6), end users are responsible for managing the SHM lifecycle in non-root standalone installations. After SHM data is collected, the host system will be able to generate an insight report that concentrates primarily on the gathered OS metrics.

Manage the SHM background process (daemon) with the following commands:

  • sysmonctl start: Start the System Health Monitor (SHM)
  • sysmonctl stop: Stop the System Health Monitor (SHM)

Note:

  • Scope: SHM within AHF for standalone, non-root installations is supported only in Oracle Restart or single-instance environments on Linux.
  • Data Capture Limitations: Operating in non-root mode imposes certain restrictions, which may lead to differences in the depth and breadth of collected data when compared to root installations.
  • Security and compatibility:
    • SHM, when running as a non-root user, gathers metrics by reading from /proc.
    • For environments running SELinux, ensure SHM operates correctly in enforcing mode without interruption or failure.