# ip-to-entity

Add machineName with ip.

# Enriched fields

Name	Type	Description
machienName	String	Name of machine.

# Prerequisites

ip-to-entity enrichment middleware needs ip. You need to find the file inist-ip.json.

You must use ip-to-entity after filter, parser, deduplicator middleware.

# Example of structure of file

{
  "ips": [
    {
			"ip": "127.0.0.1",
			"_comment": "Insititution 1"
		},
  ],
  "ipRanges": [
    {
			"from": "128.0.0.100",
			"to": "128.0.1.110",
			"_comment": "Institution 2"
		},
  ]
}

# Headers

ip-to-entity-source-field : Fields in the ec for enrichment. "ip" by default.
ip-to-entity-enriched-field : Enriched field in the EC. "institution-name" by default.

# How to use

# ezPAARSE admin page

On the /admin/middlewares page, you can choose to move the middleware from “Available Middleware” to “Active Middleware for Processing.”

# ezPAARSE process page

On the /process page, under the “2 Settings” tab, in the ‘Settings’ menu, you can choose to move the middleware from “Available Middleware” to “Active Middleware for Processing.”

# ezp

You can use ip-to-entity for an enrichment process with ezp (opens new window) like this:

# enrich with one file
ezp process <path of your file> \
  --host <host of your ezPAARSE instance> \
  --settings <settings-id> \
  --header "ezPAARSE-Middlewares: ip-to-entity" \
  --out ./result.csv

# enrich with multiples files
ezp bulk <path of your directory> \
  --host <host of your ezPAARSE instance> \
  --settings <settings-id> \
  --header "ezPAARSE-Middlewares: ip-to-entity"

# curl

You can use ip-to-entity for an enrichment process with curl like this:

curl -X POST -v http://localhost:59599 \
  -H "ezPAARSE-Middlewares: ip-to-entity" \
  -H "Log-Format-Ezproxy: <line format>" \
  -F "file=@<log file path>"

← idp-to-institution ip-to-institution →