Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
From: Igor Rudyak <irudyak@gmail.com>
Date: Wed, 13 Jul 2016 12:45:20 -0700
Message-ID: <CAMpMOYGvOv3aqTPrROp8+Rmi_=U1dq+_UoS4waWnyT9OPc=jcw@mail.gmail.com>
Subject: Ignite monitoring
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a11c030224a4e24053789a1a2
archived-at: Wed, 13 Jul 2016 19:45:51 -0000

--001a11c030224a4e24053789a1a2
Content-Type: text/plain; charset=UTF-8

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

--001a11c030224a4e24053789a1a2--