We have a huge weblogic server deployment and we are slurping up huge amounts of data from the MBeans both in weblogic and custom to our application. I was wondering if anybody would be interested in this and I will post accordingly. I would also appreciate constructive feedback on the process as well.
Ad Widget
Collapse
Interested in our methodolgy for polling JMX/weblogic data?
Collapse
X
-
I would be interested in hearing about monitoring of WebLogic and WebSphere (anyone else?) applications. Please share your experience. -
-
Well, in a separate thread a problem we have run into with the number of parameters we have created as a result of our method has exposed a bottleneck in the zabbix_agent (active) check process (which should be addressed in the next release according to Alexei). That said, after some thought I think we can definitely do a more effecient job and once I give it a revamp I think it will be ready for the community at large.
As a result, I would NOT advise anybody use our method at this time. I am going to go back to the drawing board and spend a bit of time on this issue and see if I can find a more effecient mechanism which I could in turn submit back to the community.
So while I was all happy to post away, our method has run a foul and could be done better anyway. I will share forthwith once we get it resolved. Sorry for getting everyone so excited, but it is really my fault for jumping the gun.
AaronComment
-
-
-
Greetings,
The trick is to use WLShell to query the weblogic console, then it feeds the returned JMX data to Zabbix via the zabbix-sender utility.Originally posted by gpostaireHello,
Did you post your solution somewhere in the forum ?
I try to monitor some weblogic server.
Thanks.Comment
-
wlshell latest beta supports any JMX 1.2 instance according to the release site, the primary mechanism for populating a zabbix instance via wlshell is to retrieve the Mbean value and make an external call to zabbix_sender. That is how we do it currently. I assume that since wlshell works with JMX 1.2 it would work with JBoss.Comment
Comment