If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[pulsetranslator] Migrate pulsetranslator to heroku

RESOLVED FIXED

Status

Webtools
Pulse
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: jgriffin, Assigned: jgriffin)

Tracking

Trunk

Firefox Tracking Flags

(firefox40 affected)

Details

(Assignee)

Description

2 years ago
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
(Assignee)

Comment 1

2 years ago
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.
(Assignee)

Comment 2

2 years ago
I've performed the switch over; I'll monitor for another day or two before closing this bug.
(Assignee)

Comment 3

2 years ago
This is working well, so closing the bug.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.