The code implies that 502 responses (actually all 5xx responses) are
routed to "retry" [1]. Are you not seeing that?



On Fri, Oct 14, 2016 at 11:59 AM, Jeremy Dyer <> wrote:
> I'm monitoring some micro services that sit behind an Nginx reverse proxy.
> The idea is simple I want to fire off an alert if I get a "502 - Bad
> Gateway" response from Nginx which would mean that something has caused the
> micro service to crash and then have NiFi attempt to restart the micro
> service.
> However no relationship is being invoked when a 502 response code is
> returned? Works great for 200 or even 500 but not getting any output what
> so ever for a 502? Any ideas?
> Thanks,
> Jeremy Dyer

Reply via email to