Igor, can you please share the changes to scripts you did to support monitoring? Can it be done by defining and exporting JAVA_OPTS env variable and then launching ignite.sh?
Thanks! --Yakov 2016-07-13 22:45 GMT+03:00 Igor Rudyak <irud...@gmail.com>: > Hi guys, > > While experimenting with large Ignite clusters I found that lack of > monitoring is rather critical problem. I know that Ignite provides number > of JMX MBeans to monitor custom metrics in addition to host system metrics > (CPU, IO, RAM, ....). The problem is, there are no out of the box solution > to monitor all this. > > Thus you have to manually setup some kind of monitoring tool like Graphite, > Grafana, Ganglia and etc. Which involves setting up monitoring agents on > all the nodes, uploading JMX agent on all the nodes, selecting appropriate > metrics from the plenty of JMX MBeans and preparing config files, tuning > Ignite shell scripts to include "java agent" in java launch command. Lots > of work and pain, each time you want to create new Ignite cluster. > > Probably it makes sense to have all these out of the box, by slightly > modifying existing and providing additional shell scripts, to bootstrap all > monitoring infrastructure? > > Igor Rudyak >
