Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #96244
| From | dieter <dieter@handshake.de> |
|---|---|
| Subject | Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... |
| Date | 2015-09-10 08:41 +0200 |
| References | <5c1f52f5-59d2-48dd-b2e8-3a907a517261@googlegroups.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.309.1441867332.8327.python-list@python.org> (permalink) |
Thomas Güttler <hv@tbz-pariv.de> 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.
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
From logging to files to a better solution: syslog, Sentry, Logstash, .... Thomas Güttler <hv@tbz-pariv.de> - 2015-09-09 01:33 -0700
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... dieter <dieter@handshake.de> - 2015-09-10 08:41 +0200
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... Thomas Güttler <hv@tbz-pariv.de> - 2015-09-11 00:22 -0700
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... marco.nawijn@colosso.nl - 2015-09-11 01:17 -0700
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... Thomas Güttler <hv@tbz-pariv.de> - 2015-09-15 02:37 -0700
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... jmp <jeanmichel@sequans.com> - 2015-09-11 11:02 +0200
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... Thomas Güttler <hv@tbz-pariv.de> - 2015-09-15 02:35 -0700
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... jmp <jeanmichel@sequans.com> - 2015-09-15 16:36 +0200
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... dieter <dieter@handshake.de> - 2015-09-16 07:57 +0200
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... Thomas Güttler <hv@tbz-pariv.de> - 2015-09-16 01:31 -0700
Re: From logging to files to a better solution: syslog, Sentry, Logstash, .... dieter <dieter@handshake.de> - 2015-09-12 08:36 +0200
csiph-web