Matt,
Thank you for your comments and for creating a Jira to add this
improvement. I'll take your advice on the logging bulletins, I agree
that can be done as a separate function.
Thanks,
Scott
On 04/11/2018 06:31 AM, Matt Gilman wrote:
tors you mentioned are bulletins. Bulletins are
Hey Scott,
Sorry, I misunderstood the original question. I thought you wanted to get
able to get the URL for a specific processor in the REST API. You actually
wanted the UI URL with the query parameters for the component in question.
This does require the parent Process Group ID and
Hi Matt,
No, I'm looking for the main UI URL, like so:
http://localhost:8899/nifi/?processGroupId=9e338e2f-0162-1000-969a-043d35e4c41d=
I'm using NiFi 1.5. What I'd really like is some way to know, using a
variable or attribute, that the processor which caused the error resides
within
Scott,
What version of NiFi are you running? If your running NiFi 1.x then the
parent process group ID shouldn't be necessary. The fully qualified URL of
a processor would look something like
http://localhost:8080/nifi-api/processors/9b52d2bf-0162-1000-d1ac-89e944aa1bfe
Or are you trying to
Hello community,
I'm trying to write a log when errors occur in my flow, and I want to
include the fully qualified URL to the location within my flow where the
error occurred. I know the component ID is an attribute I can use, but I
also need the processGroupId where the component is located
