Closed Bug 1097112 Opened 10 years ago Closed 10 years ago

Enable NewRelic monitoring for SUMO celery processes

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cliang, Assigned: cliang)

References

Details

(Whiteboard: [kanban:webops:https://kanbanize.com/ctrl_board/4/1848] )

Monitoring of NewRelic processes for SUMO may shed light on some of the high swap utilization on the production celery server.  NewRelic monitoring should be added the dev, stage, and production environment for SUMO.
Whiteboard: [kanban:webops:https://kanbanize.com/ctrl_board/4/1848]
Blocks: 1089629
Assignee: server-ops-webops → cliang
@rrosario:  I've added NewRelic monitoring for celery in the SUMO dev and staging environments.  Can you or someone on your team confirm that this has not affected routine operations in those environments before I make the same changes to production?
Flags: needinfo?(rrosario)
I did some manual testing (launched celery tasks for reindexing) and everything seems to be working great. Thumbs up.
Flags: needinfo?(rrosario)
I've applied the change to production.  Hopefully, we can pull some more data out of this as to what jobs are typically causing the server to go into high swap utilization.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.