Closed Bug 1117135 Opened 11 years ago Closed 11 years ago

affiliates.mozilla.org only shows 3 servers in New Relic despite being on the Generic cluster

Categories

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

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Engagement
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: osmose, Assigned: cliang)

Details

Yo! I was checking out New Relic to get some data on a 503 error that happened on Affiliates during a test run. The error came from generic6, but when I checked the server list in New Relic, it only showed generic3, generic4, and generic5. Shouldn't New Relic being showing _all_ the generic cluster servers, or am I misunderstanding something?
All of the generic web servers should now be showing up for the affiliates.mozilla.org application. It looks like some of the generic web heads got a new update of the New Relic python agent without the accompanying set of config changes needed to make it work. I've made sure that: 1. all of the generic web heads are running the latest New Relic Python agent 2. all of the generic web heads have gotten the config changes they need
Assignee: server-ops-webops → cliang
Status: NEW → RESOLVED
Closed: 11 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.