From dev-return-29891-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Jan 10 04:49:44 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 42933180718 for ; Wed, 10 Jan 2018 04:49:44 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 323F4160C3F; Wed, 10 Jan 2018 03:49:44 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6E515160C17 for ; Wed, 10 Jan 2018 04:49:43 +0100 (CET) Received: (qmail 50609 invoked by uid 500); 10 Jan 2018 03:49:42 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 50598 invoked by uid 99); 10 Jan 2018 03:49:41 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2018 03:49:41 +0000 Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 7507E1A0054 for ; Wed, 10 Jan 2018 03:49:39 +0000 (UTC) Received: by mail-lf0-f52.google.com with SMTP id h137so18239967lfe.8 for ; Tue, 09 Jan 2018 19:49:38 -0800 (PST) X-Gm-Message-State: AKGB3mLxCpLuXaiZ68jp0pY0BkmZAe6X3V5V8PwulhZdAIRXJlAoqk7g vFbLnjA+B7zCtDaeOj90AFSLteNk8s6KodBkpU0wqA== X-Google-Smtp-Source: ACJfBosfrgkWMDtTV+8g2yRLadkriH8Wlobxta9k0uQ9+gyhB3bg8j8OMSqhmQYd5uC/5u9LqET0mFWvLQpS98fjNyc= X-Received: by 10.46.101.90 with SMTP id z87mr10373797ljb.112.1515556177041; Tue, 09 Jan 2018 19:49:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.26.131 with HTTP; Tue, 9 Jan 2018 19:49:36 -0800 (PST) In-Reply-To: References: From: Alexey Kuznetsov Date: Wed, 10 Jan 2018 10:49:36 +0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Ignite logs adoption for enterprise grade monitoring tools To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="001a114cc2e091f0be056263ebd9" --001a114cc2e091f0be056263ebd9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Denis, I think it will be very useful. P.S. Minor note, I think ranges should be _000 - _999? On Wed, Jan 10, 2018 at 7:49 AM, Denis Magda wrote: > Igniters, > > As a preface, Alexey Kukushkin laid out an insightful and profound > explanation on what=E2=80=99s wrong with Ignite logs from a DevOps perspe= ctive, how > the community can easily tackle the gaps and how our efforts will be paye= d > off if we take his advice in consideration: > http://apache-ignite-developers.2346864.n4.nabble. > com/Ignite-not-friendly-for-Monitoring-td20802.html > > In short, Ignite log events (errors, warnings and non-severe messages) ar= e > not assigned unique identifiers. > Why a mature project like Ignite needs it? > > First, to have a human-friendly glossary of error messages or warnings > (see MySQL [1] and MongoDB [2] examples) that simplify troubleshooting an= d > debugging on the dev side. Actually we planned to do it back in 2016! [3] > > Second, turns out to be that popular DevOps monitoring tools such as > DynaTrace [4] and Nagios [5] can easily analyze IDs of log events and hel= p > automate their processing or trigger notifications. For instance, if =E2= =80=9Cnode > left=E2=80=9D log message was labeled with an ID then DynaTrace could det= ect that > event and by looking at overall memory usage (JMX) decide what to do next= - > just send an email to an admin or add a new node to the cluster. > > My proposal is to start putting the glossary together making Ignite ready > for enterprise grade monitoring systems and DevOps! > > As a first step, let=E2=80=99s define subsystems of Ignite spreading out = IDs > ranges among them: > - networking (discovery, communication) - 1000 - 3000 > - memory and persistence - 4000 - 6000 > - key-value, caching - 7000 - 9000 > - SQL - 10000 - 11000 > - etc. > > Is everyone with this format and overall endeavor? > > [1] https://dev.mysql.com/doc/refman/5.5/en/error-messages-server.html > [2] https://github.com/mongodb/mongo/blob/master/src/mongo/ > base/error_codes.err > [3] https://issues.apache.org/jira/browse/IGNITE-3690 > [4] https://www.dynatrace.com/capabilities/log-analytics/ > [5] https://www.nagios.com/solutions/log-monitoring/ --=20 Alexey Kuznetsov --001a114cc2e091f0be056263ebd9--