GeoEnrichIPRecord 2.3.0¶

BUNDLE¶

org.apache.nifi | nifi-enrich-nar

DESCRIPTION¶

Looks up geolocation information for an IP address and adds the geo information to FlowFile attributes. The geo data is provided as a MaxMind database. This version uses the NiFi Record API to allow large scale enrichment of record-oriented data sets. Each field provided by the MaxMind database can be directed to a field of the user’s choosing by providing a record path for that field configuration.

TAGS¶

enrich, geo, ip, maxmind, record

INPUT REQUIREMENT¶

REQUIRED

Supports Sensitive Dynamic Properties¶

false

PROPERTIES¶

Property

Description

Geo Database File

Path to Maxmind IP Enrichment Database File

Log Level

The Log Level to use when an IP is not found in the database. Accepted values: INFO, DEBUG, WARN, ERROR.

geo-enrich-ip-city-record-path

Record path for putting the city identified for the IP address

geo-enrich-ip-country-iso-record-path

Record path for putting the ISO Code for the country identified

geo-enrich-ip-country-postal-record-path

Record path for putting the postal code for the country identified

geo-enrich-ip-country-record-path

Record path for putting the country identified for this IP address

geo-enrich-ip-ip-record-path

The record path to retrieve the IP address for doing the lookup.

geo-enrich-ip-latitude-record-path

Record path for putting the latitude identified for this IP address

geo-enrich-ip-longitude-record-path

Record path for putting the longitude identified for this IP address

geo-enrich-ip-record-reader

Record reader service to use for reading the flowfile contents.

geo-enrich-ip-record-writer

Record writer service to use for enriching the flowfile contents.

geo-enrich-ip-split-found-not-found

Separate records that have been enriched from ones that have not. Default behavior is to send everything to the found relationship if even one record is enriched.

RELATIONSHIPS¶

NAME

DESCRIPTION

not found

Where to route flow files after unsuccessfully enriching attributes because no data was found

found

Where to route flow files after successfully enriching attributes with data provided by database

original

The original input flowfile goes to this relationship regardless of whether the content was enriched or not.