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
When an index gets deleted out from under Kibana, the filters aren't cleared. When a new index is created, the filter will remain in the queries but not be visible in the UI.
Steps to repro:
Start elasticsearch & Kibana
Run npm run makelogs
Create your logstash index and pin a filter on the discover tab (e.g. machine.os: xp)
Reboot your elasticsearch instance so it loses all it's data (I'm running it off gradle run so stopping and starting clears all the data).
Refresh the page in Kibana.
You'll be redirected to the management section and asked to create a default index, run npm run makelogs and re-create the logstash index. Notice the filter persists in the url.
Go to the visualize tab and try to create a new visualization, like a metric of the count. Notice the filter is still in the url but not shown in the filter bar. Your request will show the invisible filter applied.
The text was updated successfully, but these errors were encountered:
stacey-gammon
changed the title
Corrupt filter stored in state being used on the wrong index
Invisible filter applied after index deleted and re-created.
Jan 3, 2017
Kibana version: master
When an index gets deleted out from under Kibana, the filters aren't cleared. When a new index is created, the filter will remain in the queries but not be visible in the UI.
Steps to repro:
npm run makelogs
machine.os: xp
)gradle run
so stopping and starting clears all the data).npm run makelogs
and re-create the logstash index. Notice the filter persists in the url.The text was updated successfully, but these errors were encountered: