Kibana ESQL table give undifined errors when access by url or url is modified and reload

Elastic Stack Kibana
1

error_kiba_esql1
error_kiba_esql13523×1049 66.3 KB

error_kiba_esql2
error_kiba_esql23438×1213 118 KB

I've got this kind of errors when trying to share the view with some filters set by url. They happen randomly, but they consistently do once they happen the first time.
Also once they happen, even if I remove the filter, the dashboard will keep showing this error even if I remove the filters from the url.

I've notice that if I open a new browser and past the link it works at first, then it starts doing the same even in another browser.

what could be the cause?

2

Hi @Sereno_Polveroso

that's interesting.
Can you share some information about the environment:

  • the stack version
  • the ES|QL query used
  • the filter used
3

Sure, sorry my bad:

  1. The stack version is 8.17.2, I've also tried to update Kibana to 8.17.4 but the problem remains.
  2. the ES|QL query is a simple:
    FROM logs-yatap-apps* | LIMIT 10000

then in visualization configuration I use Table and 3 fields as columns always present in my docs, one of them is color mapped.

  1. the url with filter is like:
    http://kibana-internal.apps.rdmgmt01.btc.jma.local/app/dashboards#/view/c51668a6-b051-4026-99fe-a6a6a963ef34?_g=(filters:!((bool:(minimum_should_match:1,should:!((match_phrase:(testexec_id:'81592'))

but the problem appears also without after the first occurence.

It seems to be related to some variable that not load and maybe is cached somewhere? this would explain why changing browswer works for a while...

Also I'm in VPN towards my elastic instance, as soon as I'm in office I'll try if the problem will be present there, so we can see if delay in loading can be a reason exacerbated by the VPN...

4

I have tested your filter but the URL format seens to be incompatible with rison format.
Can you try again with this filter?
?_g=(filters:(bool:(minimum_should_match:1,should:(match_phrase:(testexec_id:'81592')))))