[ 
https://issues.apache.org/jira/browse/NIFI-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777792#comment-17777792
 ] 

ASF subversion and git services commented on NIFI-12230:
--------------------------------------------------------

Commit 3d607a7b6f37f1d24427e499df87362e45a3dfbb in nifi's branch 
refs/heads/support/nifi-1.x from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3d607a7b6f ]

NIFI-12230 Add configurable Log Level for IP not found in GeoEnrichIP

NIFI-12253 Route to not found relationship instead of rolling back in 
GeoEnrichIPRecord

This closes #7909

Signed-off-by: David Handermann <exceptionfact...@apache.org>
(cherry picked from commit 184757fede3e253ba47552ab8e6fe8bd75f8f49f)


> GeoEnrichIP shouldn't produce a message when an IP is not found
> ---------------------------------------------------------------
>
>                 Key: NIFI-12230
>                 URL: https://issues.apache.org/jira/browse/NIFI-12230
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Didier B.
>            Assignee: Pierre Villard
>            Priority: Major
>             Fix For: 1.latest, 2.latest
>
>
> GeoEnrichIP is a processor that convert an IP (found in the flowfile 
> attribute) to a geolocation information that it put in attributes. To do so 
> it requires a database file.
> In many environments, it's normal to have IP not found in the database 
> (internal IP, unknown IP, and so on). This is an information that concern the 
> rest of the workflow if needed.
> The problem here is that for every IP not found, GeoEnrichIP make a log warn 
> call which imply that a bulletin is emitted. This bulletin will trigger the 
> red box (upper right corner of the processor) up to the root flowgraph, 
> warning everyone working on the flowgraph that there is a problem, which is 
> not and will also emit a log that will flood the log system.
> *When an IP is not found, routing to failure is enough. No bulletin should be 
> emitted. Not finding an IP is normal and can happen several times per second.*



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to