search

instedd / telemetry_rails

GNU General Public License v3.0
0 stars 1 forks source link

Installation_uuid not splitting data as expected #102

Closed nditada closed 8 years ago

nditada commented 8 years ago

See attached. There's only 1 installation for Pollit, and all values are the same for each installation that Kibana is charting. Maybe it's a misunderstanding of how Kibana is translating the settings to the actual ES query?

screen shot 2016-02-23 at 8 29 35 pm
juanedi commented 8 years ago

The problem here is that installation_uuid is stored as an analyzed field in elasticsearch. This means that a uuid such as a3abc6af-5a21-4eed-8ec3-e6b3487a7e93 will produce 5 buckets (one for each part of the string).

What we see in that screenshot is data from a single installation displayed 5 times. This makes sense since there is currently only one pollit installation reporting to telemetry.