nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From scott <>
Subject Re: processGroupId URL
Date Sat, 07 Apr 2018 03:59:01 GMT
Hi Matt,

No, I'm looking for the main UI URL, like so:


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 processGroupId 9e338e2f-0162-1000-969a-043d35e4c41d so that I can 
build the complete URL. The URL will then be written to my log table so 
that operational users can go to the problem area with one click to 

This reminds me I have another problem with troubleshooting I wanted to 
ask about. You know the errors that are obvious with a red indicator in 
the upper right corner of a processor or process group you can hover 
over? They go away after what seems like a few minutes. I'd really love 
it they would stay persistent until some action is taken, like a user 
clears an alarm. Any way to do that? Or, at the very least, can I make 
them last a lot longer?



On 04/06/2018 07:20 AM, Matt Gilman wrote:
> 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 build a different URL?
> Thanks
> Matt
> On Fri, Apr 6, 2018 at 12:07 AM, scott < 
> <>> wrote:
>     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 within my flow, so that I can build a fully qualified
>     URL and put it into my log to make operational troubleshooting
>     easier. Does anyone have any advice on how I can get the
>     processGroupId as a variable/attribute I can include in my log?
>     Thanks,
>     Scott

View raw message