Aviator for Analysis

Aviator for Analysis is an AI-powered virtual assistant in OpenText Core Performance Engineering Analysis. It helps performance engineers accelerate investigations, troubleshoot runtime errors, and gain insights using natural language queries.

In this topic:

Overview

OpenText Core Performance Engineering Analysis uses generative AI to transform how teams approach performance analysis. It enables conversational analysis directly within the dashboard, helping users:

• Summarize trends and anomalies

• Correlate metrics

• Identify root causes of errors

• Onboard new team members faster

By reducing the time spent diagnosing issues, Aviator helps teams move quickly from detection to resolution.

Supported areas and actions

Supported	Details
Areas	Aviator is currently supported in the following area of the user interface: Dashboard Errors tab
Actions	Aviator can answer questions related to both general and specific aspects of test runs. Supported topics include: Transactions Analysis Anomalies Metric Correlations Vusers TRT (Transaction Response Time) Response Rate Throughput Hits Hosts Scripts Errors Other performance-related terms Note: The following types of queries are not supported: Entity generation, such as creating widgets, grids, or tabs. "How to" or documentation-style questions, including procedural or instructional content.

Back to top

Prerequisites

To use Aviator for Analysis, you must have the following:

• A Core Performance Engineering Aviator subscription. For details, contact your account team to participate in the beta program.

• A test run must be streamed to OpenText Core Performance Engineering Analysis from each performance engineering solution (required as the data source for handling performance-related questions and requests). For details, see Stream performance test results.

Back to top

Use Aviator

Send a request or question about an item to Aviator. Aviator uses context from the item, such as the description fields, comments, and images, to generate relevant responses.

To use Aviator:

1. Open the Dashboard page or the Errors tab.

2. In the banner, click the Aviator button to open the Aviator pane.

3. Enter a request or question in the chat box, or click one of the suggested prompts.

   For guidance on using Aviator, see Usage tips and example questions.

4. After Aviator responds, you can do the following.

   Button	Action
   Copy	Copy the response.
   Good response	Leave positive feedback on the response. This feedback helps improve Smart Assistant's responses.
   Bad response	Leave negative feedback on the response. This feedback helps improve Smart Assistant's responses.
   Copy code	Copy the code (part of the received response).

5. Continue the conversation by entering text in the chat box, or click + New topic to begin a new conversation.

Back to top

Learn more about errors

You can use Aviator to learn more about errors by accessing the error definitions and error logs.

To use Aviator to troubleshoot errors:

1. In the Runs page, select a run to analyze.

2. Click the Errors tab, or access it directly from the Dashboard using the Errors Details link.

3. Click the Aviator button in the banner to ask about overall error patterns, such as:

   • “What are the most frequent errors in this run?”

   • “Summarize root causes for all errors.”

4. Alternatively, to investigate a specific error, click the Aviator icon next to an error in the log, and ask targeted questions like:

   • “What does error -26630 mean?”

   • “What caused this error in script X?”

Back to top

Usage tips and example questions

The following are general tips for using Aviator and maximizing its benefits.

Tip	Details
Start with predefined prompts	Quickly discover powerful insights with one click. This is perfect for new users or common use cases.
Use natural language	No special syntax required; just ask your question in plain English. Example: "What caused the errors at peak load?"
Focus on a single question	Short, focused queries often get better results. Long questions are more likely to fail.
Try follow-up questions	Build on Aviator's answers. Example: “Which scripts were most affected?” or “When did it start?”.

The following are some example questions that you can ask.

Page	Subject / Request
Dashboard	Correlate metrics: "Correlate throughput with Vusers over time." Experiment with filters: Ask Aviator to filter by script, host, transaction, or error code. For example, “Identify HPS spikes on host A only."
Errors	Ask about error root causes “Identify the key findings and the possible root causes for the most frequent errors in this test run." Drill into error patterns “List common causes for -26630 errors.”

Back to top

See also:

• View the dashboard
• Investigate errors