[FR] Metric view legend abbreviation - hoover for full name

[pimdh]

Willingness to contribute

The MLflow Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature (either as an MLflow Plugin or an enhancement to the MLflow code base)?

• [ ] Yes. I can contribute this feature independently.
• [X] Yes. I would be willing to contribute this feature with guidance from the MLflow community.
• [ ] No. I cannot contribute this feature at this time.

Proposal Summary

The name of runs in the metrics view is abbreviated to 24 characters in MetricsPlotView.getLineLegend. Sometimes, only the last characters of the name disambiguate the run. A simple fix would be to have the full name of the run show when hoovering the mouse over the abbreviated name.

Motivation

This is critical to make the metrics view usable when having multiple runs whose names have the first 24 characters equal.

What component(s), interfaces, languages, and integrations does this feature affect?

Components

• [ ] area/artifacts: Artifact stores and artifact logging
• [ ] area/build: Build and test infrastructure for MLflow
• [ ] area/docs: MLflow documentation pages
• [ ] area/examples: Example code
• [ ] area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• [ ] area/models: MLmodel format, model serialization/deserialization, flavors
• [ ] area/projects: MLproject format, project running backends
• [ ] area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• [ ] area/server-infra: MLflow Tracking server backend
• [X] area/tracking: Tracking Service, tracking client APIs, autologging

Interfaces

• [X] area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• [ ] area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• [ ] area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• [ ] area/windows: Windows support

Languages

• [ ] language/r: R APIs and clients
• [ ] language/java: Java APIs and clients
• [ ] language/new: Proposals for new client languages

Integrations

• [ ] integrations/azure: Azure and Azure ML integrations
• [ ] integrations/sagemaker: SageMaker integrations
• [ ] integrations/databricks: Databricks integrations

Details

One solutions could be to implement something similar to https://codepen.io/etpinard/pen/qJgXgd as discussed in https://community.plotly.com/t/legend-tooltips/2124/2 .

[dbczumar]

@pimdh Thank you for pointing this out. We'd be very excited to review a pull request that implements the proposed solution. We're looking forward to your contribution! :)