-
Notifications
You must be signed in to change notification settings - Fork 12
-
Notifications
You must be signed in to change notification settings - Fork 12
*_geolocation using type:"geo_point" #7
Comments
Graylog currently doesn't support the geo_point mapping type, correct. |
I am interested in visualizing the geolocation fields in kibana only. May I ask where you added that part in the template please ? |
I've read documentation about custom index mapping but I can't add custom mapping to "convert" string field as geo_point. |
@matthgyver That's not possible. See @kroepke's comment for a link to the Elasticsearch documentation and the |
@joschi I'll take a look. I've think that it was possible because shanipribadi say that he have do that in the first message of this issue |
I'm triyng |
@matthgyver We are using GitHub issues for tracking bugs in Graylog itself, but this doesn't look like one. Please post this issue to our public mailing list or join the #graylog channel on freenode IRC. Thank you! |
@joschi OK sorry. |
as this is dup of Graylog2/graylog2-server#2113 this will be closed |
Hello,
I was trying out graylog2 map widget and trying to compare it with kibana map visualization. I tried to visualize the *_geolocation fields in kibana but apparently the type mapping is string, so it cannot be visualized in kibana. So I added
to _template/graylog-internal mapping.
After that all graylong geoip resolver fields are mapped as geo_point and can be visualized in kibana.
But this apparently makes it impossible to visualize the same field in graylog map widget, returning
What is the preferred way to do this?
Thank you
The text was updated successfully, but these errors were encountered: