Pinning and sorting in Kibana - volatile?

Elastic Stack Kibana
1

Dear community, my colleagues use in Kibana the feature to ping fields and sort columns.

They tell me, it works well for a few days, but then the sorting and pinning gets lost.

The wish is to do it once (it is quite some work) and then it should stay like that.

How can it be achied that these kind of settings do not get lost? And why is this the case right now?

If I define a search under discover, open the document and there pin some fields and then save this search - afterwards when loading the save the pinned field are no longer pinned.

Or the question is: Where does Kibana store if under discover a field has been pinned? A cookie?

Thank you for any insight and help!
Kind regards!

2

@smm can you confirm which version of Elasticsearch you're using? The discover screen has undergone some changes in recent versions so I would like to check.

3

Hi Carly,

that is very kind of you!

I am using version Version 8.18.8 of the Elastic stack.

What I did in detail was - mandatory is using the Edge browser:

  • Go to discover
  • Selected one document
  • Clicked on ‘Toggle dialog with details’
  • And there pinned some event fields.

Doing this in a private session and closing / reoping a session results in losing the pinned fields. Doing this in a standard session pinned fields remain.

But the information I collected in various sources tell me Kibana uses encrypted cookies and does not store information of that kind in cookies, but rather in .kibana.

Also saving a query does not save information regarding pinned fields. That woudl be the best solution!

Would you please be so kind and shed some light on the matter?

My colleague invests quite some time in pinning fields regularely. It would be cool / very helpful if this setting would not get lost (for example if by a mandatory client security rule the cache of the browser gets cleaned every few days).

Thank you very much for your help and kind regards
Stefano

4

Hi @smm,

The pinned filters from the flyout are stored in Browser Local Storage so it’s expected that they get reset when closing a private session.

What do you mean by sorting columns? In KQL/Lucene mode they are stored with the Discover session (in “search“ Saved Object then in one of .kibana indices) so they should be restorable in any new browser session.