Page MenuHomePhabricator

look at possible drupal logging snafu causing excessive log volume
Closed, ResolvedPublic1 Estimated Story Points

Description

I'm not sure why this is happening, but I noticed while investigating why we are bumping up against rsyslog rate limits on barium:

Dec 17 20:51:03 barium drupal: https://civicrm.wikimedia.org|1450385463|wmf_common|127.0.0.1|https://civicrm.wikimedia.org/index.php||1||Beginning DB transaction
Dec 17 20:51:03 barium drupal: wmf_common|1450385463|127.0.0.1|https://civicrm.wikimedia.org/index.php||1||Beginning DB transaction

I'm not sure why we would want two log entries for what appears to be the same event. Furthermore sometimes the exact same line is logged >40 times over a few minutes. Maybe they're descrete events that need to be logged individually. This ticket is to review is happening in code and make sure we're doing what we intend to.

Event Timeline

Jgreen raised the priority of this task from to Needs Triage.
Jgreen updated the task description. (Show Details)
Jgreen subscribed.
Ejegg triaged this task as High priority.
Ejegg set the point value for this task to 2.

Raising priority, as we've discovered unnecessary log lines can lead to dire consequences: T176923

Change 381152 had a related patch set uploaded (by Ejegg; owner: Ejegg):
[wikimedia/fundraising/crm@master] Delete redundant logging module

https://gerrit.wikimedia.org/r/381152

Ejegg changed the point value for this task from 2 to 1.Sep 28 2017, 8:24 PM

Change 381152 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Delete redundant logging module

https://gerrit.wikimedia.org/r/381152

Bam! That turned out to be pretty easy.