I recently upgraded all components of our logging system: logstash from
1.3 to 1.4, ES from 0.9 to 1.2 and Kibana from 3 RC1 to 3.1.
Since that upgrade however I cannot load certain dashboards anymore. I
though it might be because of the name (ID) as they often contain colons
(:).
Examples:
CUB Backoffice: IIS Logs
CUB Core: IIS Logs
However, some of them still work (the first one for example), others don't
(second one).
When browsing kibana-int with elasticsearch-head, I can clearly see a
record with "CUB Core: IIS Logs" (id & title). Searching through the index
(like Kibana does) also includes those dashboards in the search results.
I already cleared the cache for kibana-int. What else can I try?
You might have to edit the dashboards and update them as there is a number
of changes between 3 and 3.1.
We ran into this a few times, especially moving to 3.1.
I recently upgraded all components of our logging system: logstash from
1.3 to 1.4, ES from 0.9 to 1.2 and Kibana from 3 RC1 to 3.1.
Since that upgrade however I cannot load certain dashboards anymore. I
though it might be because of the name (ID) as they often contain colons
(:).
Examples:
CUB Backoffice: IIS Logs
CUB Core: IIS Logs
However, some of them still work (the first one for example), others don't
(second one).
When browsing kibana-int with elasticsearch-head, I can clearly see a
record with "CUB Core: IIS Logs" (id & title). Searching through the index
(like Kibana does) also includes those dashboards in the search results.
I already cleared the cache for kibana-int. What else can I try?
Yes, but how would I do that? Kibana won't display the dashboards.. also,
when trying to retrieve the dashboard by it's ID from Elasticsearch, it
should at least return a JSON array, right? It's not that Kibana is unable
to parse the dashboard info, ES just doesn't return it anymore for certain
keys..
When retrieving all records in the kibana-int index, it shows up, when
trying to retrieve that specific record by ID, I get the "found: false"
result.
Op maandag 2 juni 2014 13:07:56 UTC+2 schreef Mark Walkom:
You might have to edit the dashboards and update them as there is a number
of changes between 3 and 3.1.
We ran into this a few times, especially moving to 3.1.
On 2 June 2014 19:58, Maarten Ureel <maa...@ureel.be <javascript:>> wrote:
Hello,
I recently upgraded all components of our logging system: logstash from
1.3 to 1.4, ES from 0.9 to 1.2 and Kibana from 3 RC1 to 3.1.
Since that upgrade however I cannot load certain dashboards anymore. I
though it might be because of the name (ID) as they often contain colons
(:).
Examples:
CUB Backoffice: IIS Logs
CUB Core: IIS Logs
However, some of them still work (the first one for example), others
don't (second one).
When browsing kibana-int with elasticsearch-head, I can clearly see a
record with "CUB Core: IIS Logs" (id & title). Searching through the index
(like Kibana does) also includes those dashboards in the search results.
I already cleared the cache for kibana-int. What else can I try?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.