Historical job data missing on AAI Machines page for localhost machine

Products

• Automation Analytics & Intelligence

Issue/Introduction

When viewing the Machines page in Automation Analytics & Intelligence (AAI) for a machine named "localhost", you may observe the following:

• The graph correctly displays forecasted/future job runs.
• The graph shows zero data points or blank space for historical runs (before "Now").
• Searching for physical hostnames shows both historical and forecasted data correctly.

Environment

• Product: Automation Analytics & Intelligence (AAI) version 24.x
• Version: 24.x
• Scheduler: AutoSys

Cause

This behavior occurs due to how AAI correlates machine data between forecasted runs and completed run history:

1. Forecasts: The prediction engine generates forecasts based on literal strings in the scheduler's job definitions. If a job is defined with machine: localhost, AAI forecasts it under the machine name "localhost".
2. History: When an AutoSys job executes, the AutoSys agent resolves "localhost" to the physical hostname of the server. AAI records the completed run history using this physical hostname.
3. Correlation Failure: Because historical runs are stored under physical hostnames (e.g., server01.corp.com) and never under the literal string "localhost", the Machine Load chart for "localhost" finds no historical matches in the JOBRUN table.

Resolution

To ensure historical and forecasted data are correctly correlated on the Machines page, update the machine definitions to use physical hostnames or Fully Qualified Domain Names (FQDN).