ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Subject Re: Topology-wide notification on critical errors
Date Mon, 23 Apr 2018 15:14:28 GMT
Hello Denis!

In my opinion, the primary users of this improvement will be developers,
who at testing and pre-production stage are encountering errors only when
trying production-size clusters.

This means they end up with a dozen of log files and have no idea where to
start looking at. Since it's non-production, DevOps expertise is often
unavailable or limited at this point.

This is the pattern that we repeatedly see in this maillist and on SO, and


Ilya Kasnacheev

2018-04-21 1:20 GMT+03:00 Denis Magda <dmagda@apache.org>:

> It might be useful if it's supported out of the box however usually DevOps
> and admins use tools like DynaTrace or Splunk to monitor all the logs,
> arrange logs in a meaningful way and set up special hooks for particular
> events. It means if an event happens only on 1 node the tool will still
> detect it.
> Thus my question is who is a primary user of this improvement?
> --
> Denis
> On Fri, Apr 20, 2018 at 5:12 AM, Yakov Zhdanov <yzhdanov@apache.org>
> wrote:
> > Of course, no guarantees, but at least an effort.
> >
> > --Yakov
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message