Well I don't understand why it's not possible, the link you provided shows
that it actually is :o
I'm interested in visualizing these geo fileds in kibana only, so it's not
a problem that graylog doesn't support the geo_point types.
The user there claims to have just added
{
"geolocation": {
"mapping": {
"type": "geo_point"
},
"match": "*_geolocation"
}
},
in the internal template but I guess at the time the template didn't use to
overwrite the changes ?
I did the same thing by adding a template with that part but the mapping
isn't taking effects (geo fields are still string)
{
"order": 0,
"template": "graylog_*",
"settings": {},
"mappings": {
"message": {
"dynamic_templates": [
{
"geo": {
"mapping": {
"type": "geo_point"
},
"match": "*_geolocation"
}
}
]
}
},
"aliases": {}
}
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/56eec740-d99e-41fe-b505-1d9e7719f2ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
