On Wed, Jul 20, 2016 at 7:35 PM, Igor Rudyak wrote:
> Andrey,
>
> Is Web Console you are talking about the same thing as GridGain Web Console
> (http://ignite.apache.org/addons.html#web-console)? If yes it has
> monitoring tab which allows to monitor some JVM and cache metrics (
> https://console
Andrey,
Is Web Console you are talking about the same thing as GridGain Web Console
(http://ignite.apache.org/addons.html#web-console)? If yes it has
monitoring tab which allows to monitor some JVM and cache metrics (
https://console.gridgain.com/monitoring).
As for me, Visor command line tool do
Igor,
Ignite does not have monitoring in Web Console, only Configuration and SQL.
But command-line Visor in Ignite have some monitoring features and can be
used to add new.
On Wed, Jul 20, 2016 at 1:19 AM, Igor Rudyak wrote:
> Are there any documentation regarding how to use Ignite web console
Are there any documentation regarding how to use Ignite web console? How to
add new metrics to monitor?
On Mon, Jul 18, 2016 at 10:47 AM, Dmitriy Setrakyan
wrote:
> On Mon, Jul 18, 2016 at 8:45 PM, Alexey Kuznetsov >
> wrote:
>
> > I think we should have some general API and we could call it fr
On Mon, Jul 18, 2016 at 8:45 PM, Alexey Kuznetsov
wrote:
> I think we should have some general API and we could call it from web
> console and/or from other places.
>
Agree. The server side support should be sufficient to enable different
monitoring connections, including command-line visor, web
I think we should have some general API and we could call it from web
console and/or from other places.
18 Июл 2016 г. 20:18 пользователь "Dmitriy Setrakyan"
написал:
> I think we can add this functionality to Ignite web console, no?
>
> On Mon, Jul 18, 2016 at 11:08 AM, Vladimir Ozerov
> wrote
I think we can add this functionality to Ignite web console, no?
On Mon, Jul 18, 2016 at 11:08 AM, Vladimir Ozerov
wrote:
> Igor,
>
> I think that built-in monitoring facility will add great value to the
> product. We have to deal with user performance issues pretty often, and it
> is always a k
Igor,
I think that built-in monitoring facility will add great value to the
product. We have to deal with user performance issues pretty often, and it
is always a kind of pain to get to the bottom of the problem. We have to
ask users for configuration, logs, system config, etc, etc.. Instead, it
w
Yakov, as for now I just have well structured scripts to setup Ganglia
agent on Ignite hosts to monitor system metrics like CPU, RAM, IO and etc
(this scripts already included in Ignite 1.6).
Also experimented with displaying JVM metrics by providing java agent and
specifying MBeans to collect met
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 :
> Hi guys,
>
> While experimenting with large Ignite clusters I
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 soluti
11 matches
Mail list logo