1028896 - [ReMo] Enable NewRelic Celery monitoring

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Giorgos Logiotatidis [:giorgos]]

Please activate 'Background Tasks Monitoring (ie Celery Monitoring)' on NewRelic, 

 - reps.mozilla.org
 - reps.allizom.org
 - reps-dev.allizom.org

Related bug 886769

Thanks!

Comment 1

[C. Liang [:cyliang]]

I believe that I've got NewRelic reporting for celery working in the reps dev and staging environments.  =

@giorgos:  Can you please confirm that turning on New Relic reporting on celery hasn't had any unintended side effects?  If there aren't any, is there a particular good or bad time to make this change to production?  (It will require a reboot of the celery processes.)


This took longer than anticipated.  When I first tried to get New Relic monitoring integrated, the celery processes would die with a "DistributionNotFound: Unidecode" error.   The "fix" mentioned in bug 869213 was in place but didn't seem to be working.  After conferring with jakem, I installed python-unidecode to satisfy the dependency.

Comment 2

[Giorgos Logiotatidis [:giorgos]]

(In reply to C. Liang [:cyliang] from comment #1)
> @giorgos:  Can you please confirm that turning on New Relic reporting on
> celery hasn't had any unintended side effects?  If there aren't any, is
> there a particular good or bad time to make this change to production?  (It
> will require a reboot of the celery processes.)

Both dev and stage reporting works OK. No problems reported on the websites, celery jobs run as expected. Please proceed with production. Time doesn't matter, rebooting celery is fine.

Thanks!

Comment 3

[C. Liang [:cyliang]]

The changes have been applied to production.  

Please file a new bug if you discover that celery is not working correctly anymore after these changes were made.