As we know, there is one direction traffic to see whats being buffered between a RM and its GNM (nnmsubscription.ovpl) from the senders side, but we need the possibility to check on the receivers side since there are more RMs than GNMs in our customer's environment. They get cases where a particular RM drops out of the GNM cluster but its still running with over a thousand events in its queue so more information would be better.
com.hp.ov.nms.statepoller --> name=StateMapperGnmUpdateMetrics it’s a start, but its nothing that can be used for external monitoring unless customer use something like AppD to watch the JVM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.