Forum Discussion

teppotahkapaa's avatar
teppotahkapaa
Icon for Champion rankChampion
2 months ago

Dashboarding: questions and (maybe) ideas

Sorry because I am the major wrong-doer, I put quite many things in this post.

  1. Table widgets. What is the meaning of Aggergation in Metrics value. For me it seems whatever I choose from there the values are always the same, in 

    this example above table widget shown Max and lower Min aggregations, and those values are not dependent of chosen time window, seems to be the last value, always.

  2. the Aggregation in table widgets. As I as a human (would like to) understand should show the Max and Min values of the metrics from the chosen time window. Am I just understanding it wrong?
  3. Index names in table widgets. In graph it shows those index names but I have not been able to show those names in table, just values. Is that Works-as-Designed or my mistake?
  4. Help in editing dashboards? In AP2 UI all help seems to be behind Help button in the title row. Except that in some windows, for example when you are editing dashboard widgets, there is no title row -> no help available. For user that means that I have to close editing that widget, go back, press help and then go back to dashboard page/tab and start editing that widget. Not very user friendly. Is that also Works-as-Designed? 

These are from 12.3.5 + 8.20.2

3 Replies

  • teppotahkapaa's avatar
    teppotahkapaa
    Icon for Champion rankChampion
    2 months ago

    Correcting one issue, about index names, with Leaderboard Bar Chart one can show indices only. Which is actually logical, so point 3 is "solved"

  • BryanHarding's avatar
    BryanHarding
    Icon for Moderator rankModerator
    16 days ago

    Regarding #1 and #2.

    Table widgets will always show the last collected value for the selected time range. If the metric Rollup Frequency is configured for "Auto" and the time context of the dashboard is < 3 days, or statically configured to "Raw", then this metric value will be the collected value for the last poll; the Aggregation setting does not factor as there is no average, min, or max for a single collected value.

    If the metric Rollup Frequency is configured for "Hourly" or "Daily", or "Auto" and the time context of the dashboard is > 3 days, then the value presented for the metric within will be the selected Aggregation for the last respective rollup calculated within the selected dashboard time context. 

    The ask of presenting a single-value (a la table, gauge, bar, etc..) that represents the max, min, or average over the dashboard time context is only available through the Leaderboard visualization. In the case of the Leaderboard visualizations:

    Leaderboard’s displayed values are the metric’s average over the selected timespan by default. Each selected metric may be have a respective aggregation (Avg, Min, Max) as well as set to have the data point determined from either 1) Full Dashboard Timespan 2) Last Poll in the Timespan 3) Off - Not factored in Top-N calculation and displays last poll

    Regarding #4, as far as I'm aware neither the newer Help Drawer nor the page header bar have ever been presented within the dashboard widget edit experience, however, that doesn't mean that's the best experience. Do you have particular examples as to what information you'd like to see made available through the widget editor experience? Effectively the Help Drawer for dashboard's predominantly links to the online documentation and doesn't provide in-depth information within the Help Drawer itself, but understanding your pain points and the type of information driving you to the Help Drawer would be excellent context if you'd be kind enough to share.

    • teppotahkapaa's avatar
      teppotahkapaa
      Icon for Champion rankChampion
      12 days ago

      Thanks for the Min/Max info.

      About that Help Drawer question. Well: help for the widget, is the easy answer. This issue was found when trying to do those things mentioned above. Then normal logic in AP2 UI is anyway always open the new widget in same page, so if one just clicks and goes to edit a dashboard, then he/she ends up in on browser tab having that widget editor open, and if he/she then wants to have some help there, then either close the editor or open new tabs to support site and try to find it from there. 

      If there are context specific help in most of AP2 pages, then users certainly want to have that feature in all pages.  At least in those pages where one actually does some real "editing" of stuff.