Closed
Bug 1055620
Opened 11 years ago
Closed 11 years ago
Fix statsd destination on glow servers
Categories
(Infrastructure & Operations Graveyard :: WebOps: Engagement, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cliang, Assigned: pmac)
References
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1078] )
The statsd destination server has recently changed from graphite1.private.phx1.mozilla.com to graphite6.private.phx1.mozilla.com. Please update the settings for both the development and production instances of glow.
I was able to find the following references:
glow1.dev.dmz.phx1.mozilla.com
/home/mrburns/smithers/smithers/conf/server.py:
STATSD_HOST = getenv('STATSD_HOST', 'graphite1.private.phx1.mozilla.com')
glow1.dmz.phx1.mozilla.com
/data/www/webwewant.mozilla.org/project/mrburns/smithers/smithers/conf/server.py:
STATSD_HOST = 'graphite1.private.phx1.mozilla.com'
| Assignee | ||
Comment 1•11 years ago
|
||
There are a lot of sites using statsd including this one, but I manage a couple others. Does this mean that all of our (mozilla) websites have to change a setting? Do I need to file bugs for bedrock (www.mozilla.org) and basket (basket.m.o) as well?
Flags: needinfo?(cliang)
| Assignee | ||
Comment 2•11 years ago
|
||
I've updated the following servers:
glow1.dev.dmz.phx1.mozilla.com
glow1.dmz.phx1.mozilla.com
glow1.dmz.scl3.mozilla.com
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•11 years ago
|
||
I don't think that you'll need to open bugs for bedrock and basket: I *think* that I've gotten those already. I didn't make changes to the glow servers since it looked like these were managed more directly by y'all. =)
Flags: needinfo?(cliang)
| Assignee | ||
Comment 4•11 years ago
|
||
Ah. Indeed they are. Thanks!
Comment 5•11 years ago
|
||
glow1.dmz.phx1 is still sending to statsd on graphite1, perhaps services need to be restarted?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 6•11 years ago
|
||
I restarted things. Code might be behind latest. Looking at it now.
| Assignee | ||
Comment 7•11 years ago
|
||
I believe this should now be really fixed. Mind checking again :ericz?
| Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(eziegenhorn)
Comment 8•11 years ago
|
||
I don't see it at the moment, though these things aren't always constant. I'll check a few more times then declare this fixed, thanks!
Flags: needinfo?(eziegenhorn)
Comment 9•11 years ago
|
||
Looks good still, thanks.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•9 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
•