Closed Bug 1159026 Opened 9 years ago Closed 9 years ago

[pulsetranslator] Migrate pulsetranslator to heroku

Categories

(Webtools :: Pulse, defect)

Product:
Webtools
Component:
Pulse
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox40 affected)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox40 --- affected

People

(Reporter: jgriffin, Assigned: jgriffin)

Details

pulsetranslator is running on a VM in PHX1, which is going away soon.  I'm going to migrate it to heroku for it's ease of deployment and monitoring.

I already have an instance in "display-only" mode running there.  There are just a couple of issues to address:

1 - for bad pulse errors, we currently log the entire pulse message, which is too verbose for heroku's minimal built-in logging abilities, and too expensive for paid solutions
2 - I'd like to add some monitoring so we have better notification when it falls over
I've addressed these comments and added some ops docs at https://mana.mozilla.org/wiki/display/ateam/pulsetranslator.

The only thing remaining is to perform the actual cutover from the old service, which I'll try to do this week.
I've performed the switch over; I'll monitor for another day or two before closing this bug.
This is working well, so closing the bug.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.