Strange JMX monitor behavior. Flapping between up and unknown.

Update:

We found the cause of this, our firewall rule was blocking ICMP but allowing WMI for our APE.

This leaves me with the question. Does JMX monitoring rely on a successful ping before it queries WMI?

I commend Solarwinds support for being patient and helping us with optimizing our environment.

So the JMX monitors dont use ICMP or WMI.  The java application gets configured to allow JMX polling on a particular port and it sets up its own listener and the java app owners configure it for how they want it to handle authentication, could be a local user, ldap, or with an SSL cert.  So then SW uses that JMX bridge service you mentioned to handle the requests (except on linux agent based nodes where they poll jmx locally via the agent).  It's a separate thing completely than the usual WMI and ICMP polling for the rest of the server info. 

I would wager that the bug you are encountering lives inside that service and something is causing it to be inconsistent about how it polls or processes this java data.  Is there a reason you haven't upgraded to a 2024 release yet?  Its possible that whatever issue you are seeing may be fixed by now.

We did attempt upgrading to 2024 release however the JMX bridge service failed to start on the MPE, so we were forced to rollback. Haven't had the chance to clone the system and then attempt the upgrade again and then get the logs as to why the service didn't want to start but will in due to if SW support engineers don't get back to us with some info how to fix this issue.

We did attempt upgrading to 2024 release however the JMX bridge service failed to start on the MPE, so we were forced to rollback. Haven't had the chance to clone the system and then attempt the upgrade again and then get the logs as to why the service didn't want to start but will in due to if SW support engineers don't get back to us with some info how to fix this issue.