Chapter 3. Evaluate your system by using the OpenShift AI dashboard


Use the OpenShift AI dashboard to submit evaluation jobs, track results, and compare completed evaluation runs side by side. The dashboard provides a visual workflow for selecting benchmarks, configuring evaluation parameters, and viewing comparison results through the embedded MLflow interface.

3.1. Prerequisites

The following conditions must be met before you can use the evaluation functionality in the OpenShift AI dashboard:

  • You have enabled the TrustyAI component, as described in Enabling the TrustyAI component.
  • You configured MLflow experiment tracking for EvalHub. The comparison view is part of the embedded MLflow interface, so evaluation results must be logged to MLflow. For more information, see Configure MLflow experiment tracking.
  • The OpenShift AI dashboard must include the MLflow federated plugin. This plugin provides the embedded MLflow comparison view that EvalHub uses.
  • You have role-based permissions that allow you to do the following:

    • Get, list, create, update, delete EvalHub resources.
    • Create and get MLflow experiments.
  • You enabled the Evaluations page in the OpenShift AI dashboard. If it is not visible, set disableEvalHub to false in the OdhDashboardConfig custom resource (CR).

Submit evaluation jobs for your models directly from the OpenShift AI dashboard. You can configure evaluation parameters, select benchmarks or benchmark suites, and optionally set pass or fail thresholds to validate model performance against expected criteria.

EvalHub logs evaluation results to MLflow for tracking and comparison.

Prerequisites

  • You have logged in to Red Hat OpenShift AI.
  • You have a deployed model with an inference endpoint.
  • The Evaluations page is enabled in the OpenShift AI dashboard. If it is not visible, set disableEvalHub to false in the OdhDashboardConfig custom resource (CR).

Procedure

  1. In the OpenShift AI dashboard, click Develop & train Evaluations.
  2. Optional: From the Project dropdown menu, select the project namespace with the model you deployed. This filters the evaluations list to show only evaluations from the selected project.
  3. Click the Start evaluation run button and select the benchmarks to run:

    • Benchmark: Select an individual benchmark to evaluate a specific capability or task.
    • Benchmark suite: Select a predefined collection of related benchmarks to evaluate multiple aspects of model performance. Benchmark suites in the dashboard correspond to collections as described in EvalHub built-in collections.

      You can select multiple benchmarks or benchmark suites. Each selection appears as a tag below the field.

  4. Configure the basic evaluation parameters:

    • Evaluation name: Enter a unique name for the evaluation job. By default, the name is the evaluation timestamp. This name identifies the job in the evaluations list and in MLflow experiments.
    • MLflow experiment: Select an existing MLflow experiment from the dropdown menu. Evaluation results are logged as runs within the selected experiment.
    • Source: Select the source to evaluate from the dropdown menu. You can choose a model, an agent, or pre-recorded responses as a source.
    • Enter additional parameters, such as the source name, Endpoint URL, or Dataset URL, depending on the selected source.
  5. Optional: Change the evaluation threshold values by dragging the slider to select a value between 0 and 100. This value is equivalent to the 0.0-1.0 threshold used in the API.

    Alternatively, click the numeric input field to the right of the slider and type a value.

    Thresholds define pass or fail criteria for evaluation results. If you set a threshold, the evaluation results include a pass or fail status based on whether the overall score meets the specified value.

  6. Click Benchmark parameters to expand the section and configure benchmark-specific parameters. For example, if you evaluate with the Basic science Q&A benchmark, add the following parameters:

      {
        "num_examples": 10,
        "limit": 5,
        "tokenizer": "google/flan-t5-small"
      }
  7. Click Evaluate.

    The evaluation job is submitted and the page returns to the evaluations list.

Verification

  1. On the Evaluations page, locate your evaluation job in the list.
  2. Verify that the Status column shows Running while the job executes. The job progresses to Completed when all benchmarks finish successfully, or Failed if an error occurs.
  3. When the job completes, click the evaluation name to view detailed results, including benchmark scores and pass or fail status if you configured a threshold.

3.3. Evaluation run comparison

You can compare two or more completed evaluation runs side by side in the OpenShift AI dashboard. The comparison view helps you identify which metrics improved or regressed between runs without manually switching between individual result pages.

Evaluation run comparison is artifact-agnostic. You can compare runs regardless of what was evaluated: models, Retrieval Augmented Generation (RAG) pipeline configurations, agentic AI systems, prompt templates, or any other AI artifact that EvalHub supports. The comparison view presents the evaluation metrics and parameters for each run in aligned columns, so you can see how different configurations performed relative to each other.

3.3.1. Evaluation run comparison limitations

Review limitations for comparing evaluation runs in the OpenShift AI dashboard.

The following limitations apply to the evaluation run comparison view:

No score direction indicators
The comparison view does not indicate whether a higher or lower metric value is better. Metric direction, such as the lower_is_better flag set in benchmark configurations, is not reflected in the MLflow comparison view. You must interpret metric changes based on your knowledge of each benchmark.
No pass or fail thresholds
Pass criteria and thresholds that you configure in EvalHub are not displayed in the comparison view. The comparison shows raw metric values without indicating whether a run passed or failed a threshold.
No benchmark grouping for suites
When you compare runs that used benchmark suites, the comparison view does not group metrics by benchmark within the suite. Metrics are displayed as a flat list of key-value pairs.
No export capability
You cannot export comparison results to a file. To share comparison results, use the comparison view URL.
Generic key-value display
The MLflow comparison view displays parameters and metrics as generic key-value pairs. EvalHub-specific metadata, such as benchmark categories, provider information, and collection structure, is not reflected in the comparison layout.

Compare two or more completed evaluation runs side by side to identify metric differences across runs. The comparison opens the embedded MLflow comparison view, which displays parameters and metrics for each selected run.

Prerequisites

  • You have logged in to Red Hat OpenShift AI.
  • You have at least two completed evaluation runs.

What you can compare

You can compare any completed evaluation runs, including the following:

  • Runs that evaluated different versions of the same model
  • Runs that used different benchmarks or benchmark suites
  • Runs that evaluated different types of AI artifacts, such as a model and a RAG pipeline
  • Runs that used different inference parameters or evaluation configurations

The only requirement is that each run has a Completed status.

Comparison view capabilities

The MLflow comparison view provides the following capabilities:

  • Side-by-side display of parameters and metrics for all selected runs
  • Filtering to show only parameters or metrics that differ between runs
  • A shareable URL that you can send to team members for review
Note

The comparison view displays metrics and parameters as generic key-value pairs from MLflow. EvalHub-specific presentation, such as score direction indicators, pass or fail thresholds, and benchmark grouping within evaluation suites, is not available in the comparison view.

Procedure

  1. In the OpenShift AI dashboard, click Develop & train Evaluations.
  2. Optional: From the Project dropdown menu, select the project namespace to filter the evaluations list.
  3. In the evaluations list, select the checkbox next to each completed evaluation run that you want to compare.

    You can select two or more runs. The runs do not need to use the same benchmark.

  4. Click Compare.

    • If you selected runs with benchmarks, the MLflow comparison view opens and displays the parameters and metrics for the selected runs in a side-by-side layout.
    • If you selected runs with benchmark suites, the additional Choose Benchmarks step opens that lists the individual benchmarks that are included in the suites. Select the benchmarks that you want to include in the comparison and click Compare again.

      You can select all benchmarks or a subset. By selecting specific benchmarks you can compare performance on targeted capabilities, such as reasoning or safety, without including unrelated benchmark results.

  5. Review the comparison results:

    • In the Visualizations section, use the available plot types, such as parallel coordinates or contour plots, to visually compare how parameter combinations affect evaluation metrics across the selected runs.
    • In the Run details section, you can expand each run to view its configuration, status, and metadata.
    • In the Parameters section, you can compare the configuration values for each run side by side, such as the model endpoint, inference parameters, and benchmark settings.
    • In the Metrics section, you can compare the evaluation scores for each run to identify which metrics improved or regressed.

Verification

  • Verify that the MLflow comparison view displays parameter and metric data for all selected runs in the aligned columns.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top