You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on customer feedback and the balance of personal opinions, we should protect the end-user from themselves and force them to select the partitioning fields when using the Single Metric Viewer.
Currently, we show average values for all partitioning fields on page load. This has the advantage of showing something other than a warning and is usually fine for smaller/simple jobs...
However for jobs with many partitioning fields, then this can cause the single metric viewer to display many critical anomalies and be mostly red. From experience, not all end-users realise that they need to narrow the scope and pick a "single metric".
The text was updated successfully, but these errors were encountered:
I have always found this behaviour odd as well. This is the single metric viewer and I really think it shouldn't be displaying some combination of multiple metrics. Personally, I'd be happy with one of:
Don't draw the chart and display a message in its place that you need to select a metric
Have a pop up which forces you to select the metric if job is multi-metric and none is supplied when navigating to the page
Select an arbitrary (say the first) metric from the drop down and show that if none is supplied. Maybe we could somehow highlight that a metric was chosen automatically if this happened
Original comment by @sophiec20:
Based on customer feedback and the balance of personal opinions, we should protect the end-user from themselves and force them to select the partitioning fields when using the Single Metric Viewer.
Currently, we show average values for all partitioning fields on page load. This has the advantage of showing something other than a warning and is usually fine for smaller/simple jobs...
However for jobs with many partitioning fields, then this can cause the single metric viewer to display many critical anomalies and be mostly red. From experience, not all end-users realise that they need to narrow the scope and pick a "single metric".
The text was updated successfully, but these errors were encountered: