Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C3283196E2 for ; Thu, 14 Apr 2016 13:04:33 +0000 (UTC) Received: (qmail 79153 invoked by uid 500); 14 Apr 2016 13:04:33 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 79099 invoked by uid 500); 14 Apr 2016 13:04:33 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 79087 invoked by uid 99); 14 Apr 2016 13:04:32 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Apr 2016 13:04:32 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3B9AFC0D80 for ; Thu, 14 Apr 2016 13:04:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id UyZRYfbMf8ib for ; Thu, 14 Apr 2016 13:04:29 +0000 (UTC) Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 4815D5FB01 for ; Thu, 14 Apr 2016 13:04:29 +0000 (UTC) Received: by mail-wm0-f49.google.com with SMTP id n3so125117497wmn.0 for ; Thu, 14 Apr 2016 06:04:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=64zECvYM/sFPA+hxb0Pbwh6iDSGeaO5ZhzMqCtzJtMs=; b=F8ar95d77x3M38uGRXV/K9wuS+inUymcpzGp1ZS4ffsGszU0YrPHgrrIc7/yo4J9og giZ1BTvp9Z9uamkLnA/NQb3Pae0skkyjxZ7ZCbOhiRi2m6vcv1P78Hgyn4ptNUXADWPa +SCOUtRQam5H6jw8luv1zfGvf19YOu91J7lyJU1K158MfUMG7N1FaHmvl5cXwkGyJBLY /4UUg1Nfk1zvwyZlMLs3tcK3rdQPcJznm6ISemwiuDJW7N96WTjHPDJ9Zn6eQlsxtcMu o8cG2bP9ptA5MIuBn6tkkyhcYbEZ7a0MiA+4zNAO/2kviEXBDbVNP06QRv4rHHUvVzcQ lOJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=64zECvYM/sFPA+hxb0Pbwh6iDSGeaO5ZhzMqCtzJtMs=; b=Ud0gm3V66Akn3oYb3T4sJDMSYKY9STMdeNFx3l9kuvCnpr1Zlrlno1S0WSrtMEhZJv wBn21PorMKKCPPUJ5HshUX97avQUwBAEZ14sgCoGODsD7fDQ2quei1uySFtYKNXC6bwL 2/KQCKrnrWhVJV48vDsRVlLnAgTcx0GrgrdI8Zw1r2StGYnlxPJSItLZs5ogRgSdZChY ihz+qWt09lcwvgWtqyWYHdF8MKJ934tSC0LXT4AJuryFItY5S1/EQGmhB10uqWxy0f3w L2+MSoTgPTZLMLCeFLlaAlPLFxqjZoDnUg8d0u8DhBXEtyCNhY75+BAPAtR1Q8xRFQPK bXrA== X-Gm-Message-State: AD7BkJLNCHZswgXyB9s6S9d/XasdSe0JrygPzHWvOW1dQUVYkCPbmGR29PsB+OGt8L6eNdAzmbKGzjimhHI2KA== X-Received: by 10.28.29.84 with SMTP id d81mr35304208wmd.59.1460639063443; Thu, 14 Apr 2016 06:04:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.125.67 with HTTP; Thu, 14 Apr 2016 06:04:03 -0700 (PDT) In-Reply-To: References: From: Daan Hoogland Date: Thu, 14 Apr 2016 15:04:03 +0200 Message-ID: Subject: Re: [discuss] CloudStack logging To: dev Content-Type: multipart/alternative; boundary=001a114b461c858e4705307188d3 --001a114b461c858e4705307188d3 Content-Type: text/plain; charset=UTF-8 I largely agree with just one sneer to the operators amongst us: the level can be set on a per package and even class basis. So you can work through disabling anoying logging step by step. Makes sense to keep looking at the source in the meanwhile to make sure sensible diagnostics remains available. On Thu, Apr 14, 2016 at 2:49 PM, Paul Angus wrote: > Hi All > > I think that we can all agree that CloudStack logs are very difficult to > read, especially for operational staff. > > I believe that the primary reason for this is that a large amount of what > should be INFO level events are categorised as DEBUG. The logging > therefore must be set at DEBUG for the logs to capture these events. By > defaulting the logging to DEBUG we include a lot of detail which is > counter-productive when using the logs to diagnose operational issues. > > I think the situation can be greatly improved by reviewing the > categorisation of logged events and where necessary re-categorise then such > that INFO, WARN and ERROR logging would be sufficient for an 'operational' > admin. > > I think a phased approach where the default logging level remains at DEBUG > while re-categorisation occurs would mean that nothing materially changes > until we are happy with the categorisations. Then we can default the > logging level to INFO. > > > > Thoughts everyone? > > > > > Kind regards, > > Paul Angus > > > Regards, > > Paul Angus > > paul.angus@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > -- Daan --001a114b461c858e4705307188d3--