dashboard not working in kibana 5.6.2

[kgoedert]

Hi,

I installed the stagemonitor plugin for kibana version 5.6.2 stagemonitor-kibana-0.3.0-5.6.2.zip
I can see a link to stagemonitor on the left side menu, but no data is shown, but the indices on elasticsearch do have data.

On the discover link, when trying to search the spans* index, I get this error:

Error: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"script_exception","reason":"runtime error","script_stack":["org.elasticsearch.index.mapper.TextFieldMapper$TextFieldType.fielddataBuilder(TextFieldMapper.java:336)","org.elasticsearch.index.fielddata.IndexFieldDataService.getForField(IndexFieldDataService.java:111)","org.elasticsearch.search.lookup.LeafDocLookup$1.run(LeafDocLookup.java:84)","org.elasticsearch.search.lookup.LeafDocLookup$1.run(LeafDocLookup.java:81)","java.security.AccessController.doPrivileged(Native Method)","org.elasticsearch.search.lookup.LeafDocLookup.get(LeafDocLookup.java:81)","org.elasticsearch.search.lookup.LeafDocLookup.get(LeafDocLookup.java:36)","doc['trace_id'].value","    ^---- HERE"],"script":"doc['trace_id'].value","lang":"painless"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"fetch","grouped":true,"failed_shards":[{"shard":0,"index":"stagemonitor-spans-2017.11.08","node":"xNPyOeVuQIqMJy48rifwxg","reason":{"type":"script_exception","reason":"runtime error","script_stack":["org.elasticsearch.index.mapper.TextFieldMapper$TextFieldType.fielddataBuilder(TextFieldMapper.java:336)","org.elasticsearch.index.fielddata.IndexFieldDataService.getForField(IndexFieldDataService.java:111)","org.elasticsearch.search.lookup.LeafDocLookup$1.run(LeafDocLookup.java:84)","org.elasticsearch.search.lookup.LeafDocLookup$1.run(LeafDocLookup.java:81)","java.security.AccessController.doPrivileged(Native Method)","org.elasticsearch.search.lookup.LeafDocLookup.get(LeafDocLookup.java:81)","org.elasticsearch.search.lookup.LeafDocLookup.get(LeafDocLookup.java:36)","doc['trace_id'].value","    ^---- HERE"],"script":"doc['trace_id'].value","lang":"painless","caused_by":{"type":"illegal_argument_exception","reason":"Fielddata is disabled on text fields by default. Set fielddata=true on [trace_id] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead."}}}]},"status":500}
    at http://localhost:5601/bundles/kibana.bundle.js?v=15543:229:30382
    at Function.Promise.try (http://localhost:5601/bundles/commons.bundle.js?v=15543:91:15695)
    at http://localhost:5601/bundles/commons.bundle.js?v=15543:91:15065
    at Array.map (native)
    at Function.Promise.map (http://localhost:5601/bundles/commons.bundle.js?v=15543:91:15020)
    at callResponseHandlers (http://localhost:5601/bundles/kibana.bundle.js?v=15543:229:29998)
    at http://localhost:5601/bundles/kibana.bundle.js?v=15543:229:18236
    at processQueue (http://localhost:5601/bundles/commons.bundle.js?v=15543:38:23621)
    at http://localhost:5601/bundles/commons.bundle.js?v=15543:38:23888
    at Scope.$eval (http://localhost:5601/bundles/commons.bundle.js?v=15543:39:4619)

How can I get the plugin working?

[trampi]

Hi!

Is it possible, that you have started the monitored Application before starting Elasticsearch?

To solve the issue, could you do the following steps?

1. start elasticsearch
2. stop the monitored application, delete the index stagemonitor-spans-2017.11.08 (and probably any newer / older indices)
3. start the monitored application and try accessing the stagemonitor plugin in kibana?

I have opened an issue in the core stagemonitor project to fix the root cause

[kgoedert]

Hi,
I tried that but it didn't work. Something I did not say before is that everything is working inside docker containers..

[trampi]

@felixbarny any idea why the proposed workaround did not help?

[felixbarny]

No, not really :(

@kgoedert could you do a GET /_mapping/stagemonitor-spans-2017.11.08 and post the result?

[kgoedert]

I don't have the files anymore, but I will try to run the containers again as soon as possible