{"push_id":599645687,"size":2,"distinct_size":0,"ref":"refs/heads/deployed-to-preview","head":"3fa353eebabc72a4d83dfa1adadff37f352b27e1","before":"9ea33f4a36ec7aaa6acb79e18c508ed6ab3f1aaa","commits":[{"sha":"c7ecfa60ac064caf9562d579c5797838284f5abf","author":{"email":"23fd7f9af1666396a2ae0c81fe1568dd52b6809d@gmail.com","name":"Timothy Mower"},"message":"Add a request-id to all log messages\n\nFor tracing the 502 errors we are seeing.\n\nFrom kibana, we can trace an nginx 502 with a request-id to a single log\nline in stagecraft, which is when the request processing is started.\nFrom here we can get a process_id, but it is impossible to work out\nwhich log lines refer to the same request as a process can handle\nmultiple requests.\n\nThis uses the idea in\nhttps://raw.githubusercontent.com/jedie/django-tools/master/django_tools/middlewares/ThreadLocal.py\nto store the request in a thread local variable, which we can then\nreference when logging","distinct":false,"url":"https://api.github.com/repos/alphagov/stagecraft/commits/c7ecfa60ac064caf9562d579c5797838284f5abf"},{"sha":"3fa353eebabc72a4d83dfa1adadff37f352b27e1","author":{"email":"89e03b7c27e6924c88d4dd784b27dcd49b67f907@gmail.com","name":"Ben Marvell"},"message":"Merge pull request #327 from alphagov/add-request-id-to-all-log-messages\n\nAdd a request-id to all log messages","distinct":false,"url":"https://api.github.com/repos/alphagov/stagecraft/commits/3fa353eebabc72a4d83dfa1adadff37f352b27e1"}]}