-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Centralize storage of query? #186
Comments
Hi, If I understand your problem, You can create a new group for each group of panel which you want to modify with the same query. When you edit your panel you have to change the groupe of your panel to regroup this one with others. And you create a stringquery with this group. |
Hi, Please see the comment I made here : #163 (comment) Regards, |
I guess that's the right thing to do ... put them all in separate groups.
|
Currently designed this way. Working on a refactor that should address this |
milestone pre3 has a query service that coordinates all of the queries on the dashboard |
…anel The cluster panel's status now has an info icon to explain non-green state The indices stats table now takes index status into consideratio when choosing what indices to show. Indices stats table also sorts indices names with a .prefix lower then normal names. Closes elastic#143, Closes elastic#186, Relates to elastic#181
* fix: bug where element render functions could mutate redux state * fix: allow grid to work without an x dimension * chore: hoise getColor out of grid render fn there's no need to keep re-defining that function, it never changes, it simply needs the pallette value passed in
Right now the user experience is confusing between stringquery and histogram (and other panels as well).
If you alter the stringquery, it changes the histogram (good). If you edit the histogram to have nice labels for everything, then update the stringquery again, you lose all the nice labels (bad). This kind of thing happens all the time when I'm designing dashboards and there's no way to recover the lost work.
I think this happens because internally there's no central place to store the query. Each panel tries to adapt to changes that the other panels fire off, but then stores its own private copy. So when another panel makes a change and fires a "query" message, everyone else's metadata gets blown away.
Could there be a SINGLE place to store the query array for a given group which all panels can reach?
The text was updated successfully, but these errors were encountered: