Changes in this Release

This preface lists changes in the Oracle Autonomous Health Framework Fleet Insights User's Guide 25.1.0.0.

Single-Instance Support

AHF Fleet Insights now supports single-instance systems.

Many organizations use a mix of clustered and single-instance databases. Previously, AHF Fleet Insights supported only clustered environments.

With this release, AHF Fleet Insights expands its capabilities to include the registration and management of single-instance systems.

To register a single-instance system, use the standard registration command:
ahf configuration set --type fleet-insights --user-name <registration_user> --url <ahffi_app_url>

Event Time in Events Drilldown Tables

Event analysis and diagnostics have been improved with the introduction of precise timestamps in the Events Drilldown Tables.

Knowing exactly when an event occurred is essential for diagnosing issues and reconstructing system activity timelines. A new Event Time column has been added to the Events Drilldown Tables, offering detailed timing information for each event. This enhancement significantly improves visibility into system behavior, enabling more accurate diagnostics, auditing, and event correlation.

With this feature, users can more easily identify patterns, understand the sequence of critical events, and gain deeper insights into their system’s operational history.

How to View the Event Time:
  1. From the Home page, set your desired time range using the filter.
  2. Click the Events panel to open the Events page.
  3. On the Events page, click any chart or table entry to drill down into a specific event type.
  4. The Events Drilldown Table at the bottom of the page now includes the new Event Time column.

Configurable Session Timeout

AHF Fleet Insights now offers configurable session timeouts, providing a balance between enhanced security and improved user experience.

Previously, sessions were limited to a fixed 30-minute timeout, often resulting in users being logged out and needing to re-authenticate. With this update, administrators can now customize session timeout durations based on their organization’s security policies and operational requirements—up to a maximum of 24 hours (1440 minutes).

This flexibility ensures uninterrupted access for longer tasks while still allowing organizations to enforce session expiration for security compliance.

How to Set the Session Timeout

You can configure the session timeout either via the command line or the web interface:
  • Command Line:
    ahffi updateproperty -k TIMEOUT -v <minutes>
  • Web Interface:
    1. Click your login name at the top right corner of the Fleet Insights web application.
    2. Select Admin.
    3. Go to Configurations and set the desired timeout value.

Prioritized Collection Purging

AHF Fleet Insights now features an improved data purging policy that intelligently prioritizes which collections to retain, ensuring more useful data remains available for longer.

Automated purging of older collections is critical for optimizing storage and maintaining system performance. With this enhancement, AHF Fleet Insights refines its approach by assigning higher deletion priority to:
  • Older collections
  • Collections not actively used by the user interface

This means more recent and relevant data is preserved longer, giving users better access to the information that matters most—especially during troubleshooting or historical analysis.

No configuration is necessary—this enhancement is automatically applied and requires no user action.

Support for Custom Installation Temp Directory

The AHF Fleet Insights installer now supports the AHFFI_TMP_DIR environment variable, allowing users to specify a custom directory for storing temporary files during installation.

By default, the installer writes temporary files to the /tmp directory. However, this location may not always be suitable—particularly in environments with limited disk space or restrictive permissions.

To address this, users can now redirect temporary file storage to an alternative location by setting the AHFFI_TMP_DIR environment variable before running the installer.

Before running the installer, specify a custom temporary directory by exporting AHFFI_TMP_DIR=<TEMP_DIR_PATH>.