celesteflan

Sure. I've not perfected/tested this to see if this is 100% accurate, but I think I'll use some test machines and groups to make sure the logic is right ( and I can come back and edit this post with the accurate SQL). This is it so far: SELECT Nodes.Caption, Nodes.Nodeid FROM DBO.Nodes INNER JOIN…

Ended up using my SQL knowledge to set up an alert that would detect this

Oh, when I tried to set up the dependency, I got the error that the child can't be a part of the parent group. Not sure if this will work then.

Thanks! Yeah, I noticed that there wasn't really good way to link the group to the node in the alert builder which stumped me. I think understand this setup, I think it would work. But if I understand correctly I'm going to have to create a dependency for each circuit? That'll be a lot, but doable. It'll end up with around…

Thanks! I ended up fixing it with this: https://support.solarwinds.com/SuccessCenter/s/article/SAM-Powershell-not-working-after-2022-3-Upgrade?language=en_US Not sure why it would work sometimes and not others as the article seems to imply powershell wouldnt have worked at all, but this did stop the flickering status. 

Just "Unknown", I've been trying to catch it and see what the actual issue is, but whenever I test the component in the Edit Application screen, it works. 

Yeah, that's what I figured, and that makes sense. What about going to two separate pages? It would also happen if they logged in to the specific page and then tried to navigate elsewhere--they would be kicked out. It is, but there's nothing discernible in the logs, when it gets hung, there's a range of 400/500 errors but…