Dashboards: lock visualization to a specific date range
See original GitHub issueHello!
Is your feature request related to a problem? Please describe.
Right now, all visualizations are using time range selected for the dashboard. However, we want to display visualizations that show information for various time periods. For example, we have Gauge, that shows RPS for the selected time range and we would like to see three gauges: for 1, 5 and 15 minute periods (like top
program shows CPU load in Linux). However, if dashboard time range set to e.g. a week, then all three gauges will display the same value for the week.
Describe the solution you’d like It would be extremely useful if we could configure a preset time range on a visualization or visualization instance level. The relevant feature in Kibana is called a Per panel time range.
Describe alternatives you’ve considered I can’t really find an alternative for this.
Additional context We find this a very important and a must-have feature without which we just can’t effectively use the OpenSearch dashboards.
Thank you!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:14 (8 by maintainers)
Top GitHub Comments
Moved to OpenSearch-Dashboards.
Here’s a data point, if it helps.
The company I work with put a significant amount of effort into developing an ELK stack and NMS dashboards based on Elastic/Kibana. They then put a lot of effort into transitioning to OpenSearch, despite the fact that there were several Elastic/Kibana features that were not (yet?) available with OpenSearch.
When the operators learned that they would not be able to have certain charts/graphs with fixed time ranges, that effectively put the transition to OpenSearch completely on hold. It was the one feature they would/could not do without.
If users are continually asking for an established feature/functionality that appears to be “missing” compared to alternative products, it might be beneficial to give them something to work with. (…even if it isn’t perfect, isn’t a complete solution, or will eventually evolve to better tie in with a more extensive development effort…)
Also, the dashboard mockups presented earlier may be slightly misleading (i.e. pessimistic) in that they show a full date/time range. The basic Elastic/Kibana time ranges are things such as “Last 1 minute”, “Last 1 week” etc. These do not take up nearly as much screen real estate. The user also sometimes has the option of working the fixed time range directly into the visualization title if they don’t expect it to change.
I realize this one specific feature request is part of a more broadly-scoped effort and that you’re factoring in many considerations…so weight my feedback accordingly.