Merge lp:~bloodearnest/canonical-identity-provider/hi-fi-logging into lp:canonical-identity-provider/release
Status: | Rejected |
---|---|
Rejected by: | Simon Davy |
Proposed branch: | lp:~bloodearnest/canonical-identity-provider/hi-fi-logging |
Merge into: | lp:canonical-identity-provider/release |
Diff against target: |
91 lines (+7/-48) 3 files modified
Makefile (+1/-1) django_project/settings_base.py (+1/-46) requirements.txt (+5/-1) |
To merge this branch: | bzr merge lp:~bloodearnest/canonical-identity-provider/hi-fi-logging |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Canonical ISD hackers | Pending | ||
Review via email: mp+286877@code.launchpad.net |
Description of the change
Use the new logging library, talisker:
https:/
This library aims to standardise logging across our services, as well as provide structured logging. It does the following
- a standard log format
- arbitrary key=value pairs
- log to stderr, for the charm to handle files, directories and perms, etc (12 factor app)
This change:
- uses the gunicorn wrapper for make run, which sets up logging
- disable django's default logging, as it's not needed any more (and has bad production defaults, see https:/
Unmerged revisions
- 1399. By Simon Davy
-
clean up whitespace
- 1398. By Simon Davy
-
use explicit gunicorn version
- 1397. By Simon Davy
-
merging
- 1396. By Simon Davy
-
Remove manual wsgi wrapping
- 1395. By Simon Davy
-
merging
- 1394. By Simon Davy
-
Use new talisker runner
- 1393. By Simon Davy
-
basic talisker integration
- 1392. By Simon Davy
-
merging
- 1391. By Simon Davy
-
fix timezone formatting in access logger
- 1390. By Simon Davy
-
merging
On Tue, Feb 23, 2016 at 4:34 PM, Maximiliano Bertacchini project. wsgi:applicatio n --workers=2 --reload --pid=logs/ gunicorn. pid --bind=$(ARGS) --timeout=99999 --error-logfile=- --access-logfile=- bin/talisker_ gunicorn sso --devel -- django_ project. wsgi:applicatio n --reload --pid logs/gunicorn.pid --access-logfile - --timeout 99999 --workers 2 --bind=$(ARGS)
<email address hidden> wrote:
>
>
> Diff comments:
>
>> === modified file 'Makefile'
>> --- Makefile 2016-01-21 15:45:34 +0000
>> +++ Makefile 2016-02-23 10:59:30 +0000
>> @@ -151,7 +151,7 @@
>>
>> run: ARGS=0.0.0.0:8000
>> run:
>> - $(ENV)/bin/gunicorn django_
>> + $(ENV)/
>
> Is the --devel flag necessary?
For that makefile rule, yes. The defaults are production orientated,
and thus silence python's warning system (which is also what django's
default logging did before). --devel logs the warnings, which is what
we want in development, when this make target is designed to be used.
Thanks
--
Simon