I am not seeing any ‘geo_location’ field in my elasticsearch sink I want to map it to elasticsearch’s geopoint. Do I need to setup something extra here. I have created a structured event.
@leon No I didn’t do that. I will set it up now. Does the geo_location field gets populated as well after this enrichment?
If yes, then that location is based on IP right? What I want to do is set geo_location field from android-tracker(If it’s possible then tell me how?).
Because I am running kind of gps tracker in the background which sends me current location in every 1-5 minutes.
I just want to setup a simple location object which could be easily be mapped to Elasticsearch geo_point. Do I have to create my own schema or is it possible without doing all that?
Thank you so much for responding to me. Yes, I do have that schema and I
restarted the machine to start collector, enrichment and elasticsearch.
Yes, I am using stream enrich. I also have downloaded a local copy and
hosting it in our own s3 bucket. There is also no mapping for enrichment
in elasticsearch. Kindly can you please help? Also let me know if you need
any further info.
Can you confirm that you have enabled: true in your config and schema is exactly iglu:com.snowplowanalytics.snowplow/ip_lookups/jsonschema/1-0-0 (these are most common mistakes)? Do you also have any other enrichments enabled?
Again, thanks for the response. Yes I have enabled as “true”. But am not
sure what you mean by saying if this is exactly my schema. Sorry I’m
totally new to iglu server. Should I have iglu scala client running or just
hosing this schema in s3 should be good enough?
iglu:com.snowplowanalytics.snowplow/ip_lookups/jsonschema/1-0-0 My
resolver.json is the normal configuration provided in the snowplow site.
Are there specific steps to get the configured enrichments up and running?
I only need ip_lookups and none other.
There is a local mode but currently it is only used for loading the resources for testing - rather than for production. The recommendation is to host on S3/GCS/HTTP URI rather than locally.