Kibana version:
kibana-5.1.1-windows-x86
Elasticsearch version:
elasticsearch-5.1.1 / windows
Server OS version:
Windows 10
Browser version:
Chrome 55.0.2883.87 / latest
Original install method (e.g. download page, yum, from source, etc.):
download page
Description of the problem including expected versus actual behavior:
I was happily using my elasticsearch and kibana instances and playing around with the settings. I deleted all my indices and created a new one from scratch with a date field (ex: "2017-01-01T19:13:26.901Z"). Elasticsearch properly detected the date format as date. Then, I reloaded kibana and the console errors appeared. This could be related to me messing with the settings, but I believe the UI should not simply "break". I can load Timelion but none of the other pages (Dashboard, Management, etc.)
Steps to reproduce:
Errors in browser console (if relevant):
TypeError: FieldFormat is not a constructor
INFO: 2017-01-01T19:41:00Z
Adding connection to http://localhost:5601/elasticsearch
kibana.bundle.js?v=14566:118 setting active api to [es_5_0]
commons.bundle.js?v=14566:55 loading default index pattern
commons.bundle.js?v=14566:38 TypeError: FieldFormat is not a constructor
at IndexedArray.<anonymous> (http://localhost:5601/bundles/kibana.bundle.js?v=14566:25:29335)
at IndexedArray.memoized [as getDefaultInstance] (http://localhost:5601/bundles/commons.bundle.js?v=14566:2:28641)
at new Field (http://localhost:5601/bundles/kibana.bundle.js?v=14566:27:14202)
at http://localhost:5601/bundles/kibana.bundle.js?v=14566:27:12879
at Array.map (native)
at new FieldList (http://localhost:5601/bundles/kibana.bundle.js?v=14566:27:12852)
at initFields (http://localhost:5601/bundles/kibana.bundle.js?v=14566:25:11100)
at http://localhost:5601/bundles/kibana.bundle.js?v=14566:25:11324
at processQueue (http://localhost:5601/bundles/commons.bundle.js?v=14566:38:23621)
at http://localhost:5601/bundles/commons.bundle.js?v=14566:38:23888
I flushed all kibana settings from elasticsearch and re-created my indices which fixed the problem. I still believe that the UI should not bug out however.
Delete kibana related settings:
curl -XDELETE http://localhost:9200/.kibana/
We should definitely more gracefully handle this error.
@mariotacke did you have any field formatters defined, perhaps on a field that didn't exist in the new indices you created? I'm trying to figure out how to reproduce the error. Simply deleting existing indices and adding new ones didn't do it. Please let me know if you can provide any additional details!
Yeah, sorry. I wasn't very clear when I submitted the bug, was I... To be honest, I don't remember the exact steps, but I tried to mark a date field with type date when things went awry. I'll see if I can reproduce it again later.
Ok thanks @mariotacke !
I'm not able to reproduce this either. Please re-open if you notice this again.
I'm experiencing same issue, but with Kibana 6.4.1.
ditto @a1exus just started the free trial of Elastic Cloud and can't generate a report due to this error.
Started it up, importing web logs, added a fields at random, saved search, then tried to generate a report.
Most helpful comment
I'm experiencing same issue, but with Kibana 6.4.1.