Versioner sammenlignet

Nøgle

  • Linjen blev tilføjet.
  • Denne linje blev fjernet.
  • Formatering blev ændret.

...

Here, "cluster_name" is changed to "cluster_name.keyword"

Do the same for "name" to "name.keyword"

This improved the Dashboard a lot:

 

Image Added

But in several places, the red exclamation sign is still telling us that there is a problem, like:

Image Added

So we need to change the field - documented in https://www.elastic.co/guide/en/elasticsearch/reference/5.0/fielddata.html

I ran this in Kibana's Dev Console for the status field (not the request as the screenshot shows):

Kodeblok
PUT elasticsearch_metrics-*/_mapping/message
{
  "properties": {
    "status": { 
      "type":     "text",
      "fielddata": true
    }
  }
}

And got

Kodeblok
{
  "acknowledged": true
}

same for:

Image Added  Image Added

doing

Kodeblok
PUT elasticsearch_metrics-*/_mapping/message?update_all_types
{
  "properties": {
    "name": { 
      "type":     "text",
      "fielddata": true
      }
  }
}

giving us a lot of fixed rows:

Image Added

Fixing the CPU, CPU Instance, Memory etc (if they are empty). The problem here (also) seems to be that "name" is not field-data enabled. The best way is to make if field-data enabled. In Kinana Dev Console:

Kodeblok
PUT elasticsearch_metrics-*/_mapping/message?update_all_types
{
  "properties": {
    "name": {
      "type":     "text",
      "fielddata": true
    }
  }
}

Alternatively, Change all panels; change Group by clause from "name" to "name.keyword" :

Image Added

 

Well - I first used the first part - changing the field to fielddata: true, and the next morning this was a fact:

Image Added

Should have looked as this (with name replaced with name.keyword):

Image Added

No clue why the change kind of stopped at 01:00.

Tip

Read about the Elasticsearch 5.0 changes to strings her: https://www.elastic.co/blog/strings-are-dead-long-live-strings