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)
Infrastructure & Operations Graveyard
WebOps: Other
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.
Assignee | ||
Updated•10 years ago
|
Assignee: server-ops-webops → cliang
Assignee | ||
Comment 1•10 years ago
|
||
@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)
Assignee | ||
Comment 2•10 years ago
|
||
For reference, celery background tasks should now be appearing in New Relic: dev - https://rpm.newrelic.com/accounts/263620/applications/2779004/optimize/backgrounds_report stage - https://rpm.newrelic.com/accounts/263620/applications/2779107/optimize/backgrounds_report
Comment 3•10 years ago
|
||
I did some manual testing (launched celery tasks for reindexing) and everything seems to be working great. Thumbs up.
Flags: needinfo?(rrosario)
Assignee | ||
Comment 4•10 years ago
|
||
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
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•