Upstream Alerts are lost when changing Kong connections

[onematchfox]

I recently started monitoring multiple instances of Kong from a single Konga instance. I noticed that any upstream alerts that are configured seem to get lost/are cleared when swapping Kong connections.

I know this is "Beta" functionality but thought I'd raise this issue anyway. I will see what I can do about trying to fix the issue myself, but am not familiar with this codebase so may take me a little while; so, if anyone else out there can help, then please feel free to do so.

Also, I noticed that this seems to be linked to the loading of upstreams(?); if node 2 does not contain any upstreams then you can swap back and forth and the alerts on node 1 are maintained. But as soon as node 2 contains an upstream, any alerts seem to be lost.

1. Node 1
   

2. Node 2: note - you do not have to setup an alert here to reproduce - I have just done this to highlight the connection. You can simply load the upstreams page and then change your connection back to node 1.
   

3. Back to node 1
   

[bbebse]

+1