Kibana not loading certain dashboards after upgrades


(Maarten Ureel) #1

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).

For the non-existing dashboard, ES returns this:

{"_index":"kibana-int","_type":"dashboard","_id":"CUB Core: IIS Logs","found":false}

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?

Regards

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4452fa07-92cf-46b2-a488-e525b06a8b50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Mark Walkom) #2

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.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 2 June 2014 19:58, Maarten Ureel maarten@ureel.be 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).

For the non-existing dashboard, ES returns this:

{"_index":"kibana-int","_type":"dashboard","_id":"CUB Core: IIS Logs","found":false}

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?

Regards

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/4452fa07-92cf-46b2-a488-e525b06a8b50%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/4452fa07-92cf-46b2-a488-e525b06a8b50%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624Z%3D-aCOZF9ydo7MTCCPCE5nVpzKed_CVo_HjzRpkbC6kg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(Maarten Ureel) #3

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.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com <javascript:>
web: www.campaignmonitor.com

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).

For the non-existing dashboard, ES returns this:

{"_index":"kibana-int","_type":"dashboard","_id":"CUB Core: IIS Logs","found":false}

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?

Regards

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/4452fa07-92cf-46b2-a488-e525b06a8b50%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/4452fa07-92cf-46b2-a488-e525b06a8b50%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/12def61c-460d-4954-8af4-b52f9f3d26c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #4