Kibana 4.5.1: filter panel not appearing under search box

[test-in-prod]

Kibana version: 4.5.1

Server OS version: Windows Server 2012 R2

Browser version: Chrome 51.0.2704.103 (Official Build) m (64-bit) / Firefox 47

Original install method (e.g. download page, yum, from source, etc.): Download, running via NSSM

When adding a filter to a search in "Discover" tab, actual filters do not appear. There is no way to remove the filters and you get "No results found" if you apply too many filters. The only workaround now is to remove Json _g variable from the URL and start over from scratch.

What should happen (from official docs)

[ebsackowitz]

This is still a problem in 4.6 and extremely frustrating. In some boards it works, others it does not. In Chrome - windows.

[Bargs]

@ebsackowitz what version of 4.6 specifically? Any errors in the browser console? Do you have steps to reproduce?

Might be related to #7767

[anhlqn]

• Kibana 4.6.1
• Windows 2012 R2
• Chrome 57

I ran into this issue a few times and get one today. It may be caused by an invalid filter when we try to modify the JSON code via Export/Import as in https://stackoverflow.com/questions/36498479/kibana-dashboard-filter-bar-is-not-visible. In my case it's the wrong index pattern in the filter portion.

Cleaning up the filter part in JSON editor and re-adding filters solved my issue. I hope that Kibana throws some error messages instead of just silently hiding the filters

[cockcrow]

Also ran into this problem after I upgraded Kibana from 5.2.0 to 5.3.0 using deb package.
It could be resolved by removing the old saved filter from Saved Objects, just as @ahardy said.

Hope helps.

UPDATE
Maybe it was the index pattern?
I just rename one index pattern from celery to celery_*, for I am used to use alias but now use pattern names. Other dashboards with fixed index name did not fall into the problem, just the one with wildcard *.
Just a guess.

[test-in-prod]

Correct, resolves this as well by changing object properties (e.g. saved search). Really needs to be a better way to do this and/or a message that the old pattern is invalid.

[timroes]

This issue seems to be outdated - closing it. Please feel free to comment if you are still seeing this issue with more recent Kibana versions.

[cooniur]

@timroes I'm seeing the same issue in Kibana 5.6.4. The filter panel doesn't show up at all on the Discover page all the time.

Kibana Version: 5.6.4
Chrome Version 65.0.3325.181 (Official Build) (64-bit)
Safari Version 11.1 (13605.1.33.1.2)

Btw it works in Kibana 5.4.1.

============

Added more details:

After some investigation, It seems to be caused by importing a saved search that was created in another Kibana running against a different Elasticsearch Server.

We recently upgraded into a newer version Elasticsearch cluster and Kibana (5.6.4). We replicated the same log indices to the newer cluster with the same prefix (foobar_logs*). The saved searches from the older Kibana (5.4.1) were exported to a json file which was later imported to the newer Kibana.

During the import, Kibana prompted "The following saved objects use index patterns that do not exist. Please select the index patterns you'd like re-associated them with.", and I chose the correct index patterns.

After importing, I opened the saved search in Discover page and added some filters, but the filter panel didn't show up, and console showed an error message:

Error: Could not locate that index-pattern (id: foobar_logs*), [click here to re-create it](#/management/kibana/index?id=foobar_logs%252A&name=)
    at updateFromElasticSearch (kibana.bundle.js?v=15571:27)
    at kibana.bundle.js?v=15571:27
    at processQueue (commons.bundle.js?v=15571:38)
    at commons.bundle.js?v=15571:38
    at Scope.$eval (commons.bundle.js?v=15571:39)
    at Scope.$digest (commons.bundle.js?v=15571:39)
    at Scope.$apply (commons.bundle.js?v=15571:39)
    at done (commons.bundle.js?v=15571:37)
    at completeRequest (commons.bundle.js?v=15571:37)
    at XMLHttpRequest.xhr.onload (commons.bundle.js?v=15571:37)

[timroes]

Could you be more specific on which screens it doesn't show up? Because there are some visualizations that actually on purpose hide it, but on Discover this should always show.

[cooniur]

Hey @timroes , I just edited my previous comment with more details. It seems to relate to saved objects export/import issues.

[timroes]

@cooniur Thanks for that information. Have you actually tried to recreate that index pattern for foobar_logs*, by using the provided link #/management/kibana/index?id=foobar_logs%252A&name= on your Kibana instance? Because as it seems your index pattern is just not there, meaning everything is kind of broken at that moment :)

[cooniur]

@timroes Yes, actually I recreated the same index pattern with the same prefix in the new Kibana before importing the exported json file.

[timroes]

But that way it might get a different id. You must make sure the id of the saved object is actually foobar_log* in your case. The above link would guarantee that, or by manually specifying an id when creating it (was that even available in 5.6.x?)

[cooniur]

Yes, I figured the same. After recreating the index pattern with foobar_log* as the ID, and reimport the saved search, the filter panel started showing up. The link doesn't seem to guarantee the ID.

Actually, during the import, there is a Index Pattern Conflicts dialog pop up and asked me to choose index patterns you'd like re-associated them with.. I would assume this step should fix the ID issue automatically. Can you try to reproduce it and see if there's really a bug please?

[timroes]

@elastic/kibana-management You are aware of the above index pattern conflicts? I am not too well known with the import and migration process, sorry.

But I'll leave this issue then closed, since the actual filter bar issue, seems to be solved if the index pattern is configured correctly :)

[cooniur]

Thanks @timroes ! Makes sense to leave this issue closed as my issue seems to be caused by this import/migration issue.

I'll wait for the ES/Kibana management's reply. :)

[chrisronline]

@cooniur Can you provide your import file that isn't importing properly?