Enable NewRelic monitoring for SUMO celery processes

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: Other
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: cyliang, Assigned: cyliang)

Tracking

Details

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

(Assignee)

Description

3 years ago
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.

Updated

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

Updated

3 years ago
Blocks: 1089629
(Assignee)

Updated

3 years ago
Assignee: server-ops-webops → cliang
(Assignee)

Comment 1

3 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

3 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
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

3 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
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.