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
Whenever we report on average click position, it should have exactly 1 rounded decimal digit after the decimal point., so for the example, 15.0, 11.7, 10.7.
Having the same number of digits makes it easier to scan, and more than one decimal digit is pretty much meaningless.
Makes sense. However, I am not aware of an option to round to one decimal number. So this is a limitation in OpenSearch Dashboards not the dashboards themselves.
In a table where we have queries listed, the column width should be something reasonable (say 35) and wrap if it’s more. This makes it easier to scan.
We shouldn’t have large amounts of whitespace on the right side of the table.
Changing the size is a easily done via editing and dragging the size icon. I don't know what a size of 35 means but we can make it smaller and put the two query related charts in one line together with the most common search results. That will reduce the whitespace to the right of the table .
Why is the x axis of viz_queries_by_time_of_day labeled “filters” and not “hour of day”? Similarly for day of week.
Need to add an x-axis label for the two visualizations.
Update: Looks like we cannot define a custom label for the x-axis.
What does timestamp per day mean? Is that queries per day? Why is there a grey column at the far right of this image?
Need to switch to a better label. Instead of timestamp per day we should say queries per day. The grey column means that there may only be partial data for this time. See screenshot, taken hovering over the grey bar. It's an OpenSearch Dashboards default.
For the bargraph y axis, all numbers should have the same number of digits. It looks like xx.x makes sense for DCG, and 0.xx for NDCG and Precision.
This appears to be nothing we can influence. There are always three decimal places unless a zero is the last one. In that case the last decimal place is not shown.
I don’t think that OpenSearch dashboard restricts us to having all panes the same size. We should take advantage of that.
This will be partially addressed when we move all tables to be in the same line. Additional suggestions are always welcome.
Updated dashboard visualizations:
Changes:
Visualizations now don't have the same width
Tabular visualizations show less whitespace on the right
updated x-axis labels for Click Position Histogram & Queries over Time
Top half:
Bottom half:
The text was updated successfully, but these errors were encountered:
Some data tables remain with three decimals as there appears to be no easy way to express the same visualization that allows setting the number of decimals.
From Stavros' mail:
Makes sense. However, I am not aware of an option to round to one decimal number. So this is a limitation in OpenSearch Dashboards not the dashboards themselves.
Changing the size is a easily done via editing and dragging the size icon. I don't know what a size of 35 means but we can make it smaller and put the two query related charts in one line together with the most common search results. That will reduce the whitespace to the right of the table .
Need to add an x-axis label for the two visualizations.
Update: Looks like we cannot define a custom label for the x-axis.
Need to switch to a better label. Instead of
timestamp per day
we should sayqueries per day
. The grey column means that there may only be partial data for this time. See screenshot, taken hovering over the grey bar. It's an OpenSearch Dashboards default.This appears to be nothing we can influence. There are always three decimal places unless a zero is the last one. In that case the last decimal place is not shown.
This will be partially addressed when we move all tables to be in the same line. Additional suggestions are always welcome.
Updated dashboard visualizations:
Changes:
Top half:

Bottom half:

The text was updated successfully, but these errors were encountered: