Aviator for Analysis

Aviator for Analysis is an AI-powered virtual assistant that helps performance engineers investigate issues, troubleshoot runtime errors, and gain insights using natural language queries.

Overview

Aviator uses a multi-agent generative AI workflow to support performance analysis and provide performance engineering insights.

Aviator provides the following functionality:

  • Summarize trends and anomalies.

  • Correlate metrics.

  • Identify possible root causes of errors.

  • Generate dashboard widgets.

  • Explore analysis workflows using predefined prompts.

The Predefined section provides prompts for common analysis workflows that you can use without losing the context of the current conversation.

Supported areas and topics

Aviator is currently supported in the Dashboard and the Errors tab.

Aviator can answer questions related to both general and specific aspects of test runs. Supported topics include: Transactions, Analysis, Anomalies, Metric correlations, Vusers, Transaction Response Time (TRT), Response rate, Throughput, and Hits.

AI query usage

AI query usage is tracked at the tenant level and reported through the Core Performance Engineering Platform. The AI Usage report provides aggregated visibility into AI query consumption across supported products.

For details on viewing AI usage and exporting usage reports, see AI Usage report in the OpenText Core Performance Engineering Help Center.

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. This provides the data source for performance-related questions and requests. For details, see Stream performance test results.

Use Aviator

Ask Aviator questions about your performance test results, or use predefined and suggested prompts to explore the data.

To use Aviator:

  1. Open the Dashboard or Errors tab.

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

  3. Enter a request or question in the chat box, or select a suggested prompt.

    Alternatively, click View predefined prompts to browse predefined prompts. Select a prompt to add it to the message input box, where you can review or edit it before sending.

  4. After Aviator responds, you can select a suggested prompt to add it to the message input box for review or editing before sending. Alternatively, click + New topic to start a new conversation.

    For guidance on creating effective prompts, see Usage tips and example questions.

    For details on managing prompts, see Manage prompts.

Dashboard widgets

Use Aviator to create dashboard widgets by describing the widgets you want or by using a predefined prompt.

To create dashboard widgets:

  1. On the Runs page, select a run and open the Dashboard tab.

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

  3. Do one of the following:

    • Describe the widget you want to create in the chat box. You can create multiple widgets in a single prompt by describing each one. To receive key performance insights in the same response, ask Aviator to explain or summarize the data.

    • Select a predefined widget prompt. For example, click Show me the heaviest transactions to add a widget showing the average response times of the five heaviest transactions. The widget uses advanced filtering and sorting and supports all break-bys and filters, including those not available in the user interface, as well as multiple metrics.

    Note:  

    • You can create new widgets, but you cannot edit existing widgets using Aviator.

    • Standard dashboard widget limits still apply.

    • Measurement constraints may affect widget generation.

Troubleshoot errors

Use Aviator to investigate overall error patterns or troubleshoot a specific error.

To troubleshoot errors:

  1. On 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.

    For example:

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

    • “Summarize root causes for all errors.”

  4. To investigate a specific error, in the log entry for the error, click the Aviator icon Aviator and ask targeted questions.

    For example:

    • “What does error -26630 mean?”

    • “What caused this error in script X?”

Usage tips and example questions

The following tips can help you use Aviator effectively.

Tip Details
Start with predefined prompts

Use predefined prompts to get started with common use cases.

For details on using prompts, see Manage prompts.

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. For example, “Which scripts were most affected?” or “When did it start?”

The following are example questions that you can ask.

Page Subject / Request
Dashboard
  • Create a widget and request insights:

    “Create a widget for Hits per second and Throughput, and tell me what you observe.”

  • 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.”

Manage prompts

You can edit and retry prompts, and use predefined prompts and suggestions using the following actions.

Action Description
Edit last prompt
  • Edit the last prompt sent without retyping or reconstructing complex queries.

  • Reuse any previously sent prompt in the same chat session by copying and pasting it into other contexts or chats.

Note:

  • Editing is only available for the last message in each chat session and becomes accessible after a page refresh or navigation between tabs or pages. Editing is not supported for older prompts.

  • Only the last edited prompt is retained; previous versions are not stored.

  • Edited messages are not marked as edited.

Retry last prompt

Retry the last prompt for any prompt that was stopped, halted, or failed.

Note: This option is not available for successful prompts or prompts stopped manually by the user.

Use predefined prompts and suggestions

Use predefined prompts to get started with common tasks or add a prompt to an existing conversation without losing its context. As the conversation progresses, suggestions for relevant next steps are generated based on the current context and conversation history.

Selecting a predefined prompt or suggestion adds its text to the message input box without sending it. You can review or edit the prompt before sending.

See also