Re: How to identify MiNiFi source edge devices

Jeff, That’s a great explanation and a common thought exercise scenario we’ve used when planning other features of MiNiFi. I think what Andre suggested below would be the easiest and most successful way to accomplish what you are looking for. UpdateAttribute will let you get as specific as you

Re: How to identify MiNiFi source edge devices

Aldrin, To simplify it, the situation is analogous to a deployment of temperature sensors. Each sensor has a unique ID that is assigned by us at deployment time and each sensor periodically adds a new row to a database table that is stored on the sensor. Each sensor uses the same database schema

Re: How to identify MiNiFi source edge devices

Jeff, Could you expand upon what a device id is in your case? Something intrinsic to the device? The agent? Are these generated and assigned during provisioning? How are you making use of these when the data arrives at its desired destination? What you are expressing is certainly a common

Re: How to identify MiNiFi source edge devices

Jeff, That would be next suggestion. :-) Cheers On Wed, Apr 26, 2017 at 1:04 AM, Jeff Zemerick wrote: > It is possible. I will take a look to see if the hostname is sufficient > for the device ID. > > I just learned about the Variable Registry. It seems if I use the

Re: How to identify MiNiFi source edge devices

It is possible. I will take a look to see if the hostname is sufficient for the device ID. I just learned about the Variable Registry. It seems if I use the Variable Registry to store the device ID it would be available to the UpdateAttribute processor. Is that correct? Thanks, Jeff On Tue,

Re: How to identify MiNiFi source edge devices

Jeff, Would if be feasible for you use UpdateAttribute (which I believe is part of MiNiFi core processors) and use the ${hostname(true)} Expression language function? More about it can be found here: https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#hostname Cheers On