Path: csiph.com!news.swapon.de!feeder.erje.net!1.eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!nzpost1.xs4all.net!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.007 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'handler': 0.04; 'messages.': 0.04; 'framework.': 0.07; 'files:': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:files': 0.09; 'python': 0.10; 'ignore': 0.14; 'received:80.91.229.3': 0.16; 'received:dip0.t-ipconnect.de': 0.16; 'received:plane.gmane.org': 0.16; 'received:t-ipconnect.de': 0.16; 'unhappy': 0.16; 'vpn': 0.16; 'filtering': 0.22; 'fit': 0.23; 'header:User-Agent:1': 0.26; 'header:X-Complaints-To:1': 0.26; 'logging': 0.27; 'values': 0.28; 'remotely': 0.29; 'environment': 0.29; 'problem': 0.33; 'similar': 0.33; 'info': 0.34; 'could': 0.35; 'necessary.': 0.35; 'possible,': 0.35; 'quite': 0.35; 'level': 0.35; 'but': 0.36; 'instead': 0.36; 'there': 0.36; 'framework': 0.36; 'to:addr:python-list': 0.36; 'subject:: ': 0.37; 'received:org': 0.37; 'files': 0.38; 'why': 0.39; 'format': 0.39; 'easily': 0.39; 'to:addr:python.org': 0.40; 'received:de': 0.40; 'customer': 0.62; 'per': 0.62; 'thomas': 0.63; 'day.': 0.63; 'our': 0.64; 'respect': 0.65; 'received:217': 0.66; 'future.': 0.67; 'filtered': 0.84; 'dozen': 0.91; 'subject:From': 0.97 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: dieter Subject: Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... Date: Thu, 10 Sep 2015 08:41:45 +0200 References: <5c1f52f5-59d2-48dd-b2e8-3a907a517261@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: pd9e09977.dip0.t-ipconnect.de User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.22 (linux) Cancel-Lock: sha1:EkNTojjD1rrXXfrLJI5qJp9I9nU= X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 31 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1441867332 news.xs4all.nl 23820 [2001:888:2000:d::a6]:35041 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:96244 Thomas Güttler writes: > ... > Why we are unhappy with logging to files: > > - filtering: We don't want to get INFO messages over the VPN. You can quite easily control at what level messages are logged with the standard Python logging framework. Each handler has a level and will ignore messages at a lower level. > - Rotating: Rotating files is possible, but somehow cumbersome. There are standard tools to rotate logfiles. > - Support structured logging of values (json) in the future. Again, the Python logging framework is quite flexible with respect to the format of logged messages. > ... > Which solution could fit for our environment? I work for a customer with a similar environment (he uses "Zope" instead of "Django") - and he uses logfiles. The logfiles are automatically rotated and there are in the order of half a dozen to a dozen logfiles per day. When I have to analyse a problem with the help of the logfiles, I do not copy them via VPN but do the filtering remotely and only copy the filtered portion, if necessary.