Replies: 1 comment 1 reply
-
Thanks for the suggestion and resources, your advices are really precious. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I reckon the speedup improvement that comes from using local MMDB-based geolocation is priceless, but the trade-off is that its coverage will obviously never be 100%. For that reason, I would suggest using a fallback API-based geolocation lookup (or two) that could fill in some of the holes left.
Of course that introduces some latency and may be require some sort of background processing in order not to interefere with realtime monitoring responsiveness, but I guess users may be informed of this and be able to choose to explicitly enable this feature in the settings pane.
Some geolocation providers that do not require an API key (which I guess is a unnecessary burden for most end users) while at the same time providing good precision are RIPE IPmap and ip-api.
Beta Was this translation helpful? Give feedback.
All reactions