https://pulp.plan.io/https://pulp.plan.io/favicon.ico2016-09-21T20:00:33ZPulpPulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=146432016-09-21T20:00:33Zbmbouterbmbouter@redhat.com
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-4 status-11 priority-6 priority-default closed" href="/issues/2154">Refactor #2154</a>: Convert task system to use django models</i> added</li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=147572016-09-30T20:28:16Zbmbouterbmbouter@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/14757/diff?detail_id=15524">diff</a>)</li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=147582016-09-30T20:29:36Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Groomed</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=148152016-10-03T13:47:14Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>27</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=148412016-10-03T20:17:59Zbmbouterbmbouter@redhat.com
<ul></ul><p>This story is written at a very low level. To express what is really important it is that the celery logs need to be handled the same way that pulp logs all non-celery stuff.</p> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=152362016-10-21T16:16:16Zfdobrovofdobrovo@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>fdobrovo</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=152832016-10-24T14:29:04Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>27</i> to <i>28</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=154482016-11-01T17:13:48Zfdobrovofdobrovo@redhat.com
<ul></ul><p>WIP - <a href="https://github.com/pulp/pulp/pull/2809" class="external">https://github.com/pulp/pulp/pull/2809</a></p> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=157322016-11-11T19:29:27Zfdobrovofdobrovo@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=159062016-11-18T21:51:26Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>28</i> to <i>29</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=160502016-11-28T21:34:42Zbmbouterbmbouter@redhat.com
<ul></ul><p>I'm adding some checklist items to this.</p>
<p>Note that we had written a custom logger which on 3.0-dev is current housed at <code>pulp.app.logs</code></p>
<p>I wrote this story originally to configure the logger at pulp.app.logs, but from the PR posted I think replacing our custom logger with the Django logger itself may be better. I would be very surprised if our custom logger was better than the Django logger.</p>
<p>See this related convo: <a href="https://github.com/pulp/pulp/pull/2862/files#r89887158" class="external">https://github.com/pulp/pulp/pull/2862/files#r89887158</a></p> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=162612016-12-06T19:09:57Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>29</i> to <i>30</i></li></ul><p>This is at POST but it needs more work so moving to Sprint 12.</p> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=185502017-03-16T15:06:21Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>30</i> to <i>36</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=190242017-04-07T11:34:33Zfdobrovofdobrovo@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Set celery logger to pulp logger closes #2275 https://pulp.plan.io/issues/2275" href="https://pulp.plan.io/projects/pulp/repository/pulp/revisions/8bead7b19cf40e1b54bf9fd9658d14c4e28420df">pulp|8bead7b19cf40e1b54bf9fd9658d14c4e28420df</a>.</p> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=258542018-03-08T23:05:59Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 17</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=258792018-03-08T23:06:35Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>36</i></del>)</li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=417172019-04-25T16:47:06Zdaviddavis
<ul><li><strong>Sprint/Milestone</strong> set to <i>3.0.0</i></li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=430742019-04-26T20:39:39Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Pulp 3</i></del>)</li></ul> Pulp - Task #2275: Configure Celery to log using the Pulp syslog handlerhttps://pulp.plan.io/issues/2275?journal_id=506202019-12-13T17:16:25Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul>