Data Table is missing from model experiment page

Summary

In older version of GitLab, the mlflow paramater data was available in a table that could be sorted. This data still exists, but is only available in a csv that the user must download and leave GitLab UI to view.

Steps to reproduce

Run an MLFlow experiment in gitlab. It should have one metric and other parameters as needed.

Example Project

See this project for code and results, but it is based on this project that has the code but nothing populated in Model experiments yet

What is the current bug behavior?

There is no data table except for the csv you can download to see all of the runs and their data. The performance graph is great but the x-axis and the hover-over text do not give you information you can use to determine which run you are looking at on the graph. You must open the csv and then you can find the MLFlow ID for the run you like.

What is the expected correct behavior?

There should be a data table that lists the params collected using mlflow that can be sorted on the model experiments screen

Relevant logs and/or screenshots

See this video for how the data table used to be displayed and work

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

  (For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`)  (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`)   

Results of GitLab application Check

Expand for output related to the GitLab application check

 (For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`)  (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`)  (we will only investigate if the tests are passing)  

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.