Geo location by Exceptionless

[mgnslndh]

Have you considered adding support for geo locating events? Exceptionless would do the geo location lookup on the server side.

[niemyjski]

Not sure what you mean by geo locating events. We do have events populating the geo information and we are indexing it as geo. We do have the ability to do aggregations on geo and I'd love to have charting for this in the next generation ui (https://be.exceptionless.io/next) What would you like to see?

[mgnslndh]

Sorry for perhaps not using correct terms, but it seems you already support "geocoding" events by either setting the coordinate or an IP address in the Geo property of the event.

However, I tried both and it does not seem to affect the UI. What would be the expected result in the UI when either an IP address or a coordinate is provided? I could not find much information about this in the docs.

[niemyjski]

The ui does not currently display this information, we are building the next generation user interface and I'd love to surface this information. You however can use geo range based searches via our search box. I noticed it wasn't documented in the docs (exceptionless/Website@2f1e00a) but it's supported in the next gen ui. https://exceptionless.com/docs/filtering-and-searching/

[niemyjski]

Is there anything specific you would really like to see?

[mgnslndh]

OK, I think it would be useful to display information such as Country, Region, City as a section in one of the tabs. If you enable this it might be worth considering making it possible to provide the location related information on the client. When I look at different geo location services they do provide varying degrees of correctness. In the case the service you are using doesn't provide detailed enough lookup it could be nice if the API lets you make any lookup you want to fill in the details yourself.

So, a Geo property that works just like today. Either a coordinate or an IP address. Those values can be used on the backend to look up a bunch of location related properties. All those properties should be "Known" and a client plugin should be able to set them instead of the Geo property.

However, as a bare minimum it would be nice to see the long/lat coordinate from the Geo property (or resolved from IP) even in the current UI. That way you can at least do a manual lookup if you need to.

[niemyjski]

You have the ability to set the geo field on the client. if not specified it resolves from ip addresses on the request info, environment info and or who submitted the event.