Closed Bug 1013835 Opened 11 years ago Closed 9 years ago

Implement monitoring on the ad-hoc contributor logger

Categories

(Webmaker Graveyard :: DevOps, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: adam, Assigned: johns)

Details

Now that this is being used by MoCo and MoFo, we should setup some monitoring for this app: https://adhoctribution.herokuapp.com @JP, what do you recommend for this?
I'm setting up an endpoint monitor that will tell us if the app is up and how quickly that page loads. For more intensive app-level monitoring, I'd look at adding that to newrelic! What do you want to watch? That is publicly viewable here, and can alternatively alert you if it goes down. (I'll be notified, even if you aren't). I'll get some monitoring up on your database too and add it to that viewport. http://opsview.mofoprod.net:3000/viewport/Metrics
Status: NEW → ASSIGNED
Awesome! Let's add some NewRelic tracking as well. What do I need to do for that?
$ heroku config:set NEW_RELIC_LICENSE_KEY=licensekeyiwillgiveyou $ heroku config:set NEW_RELIC_APP_NAME=gitribution-production $ heroku config:set NEW_RELIC_APDEX=<0.010> I filed this PR to complement this: https://github.com/adamlofting/gitribution/pull/3
Here's the same for adhoctribution: https://github.com/adamlofting/adhoctribution/pull/5 Same commands, with the same license key but different names. Let the charts floweth.
Closing this out as we move to deprecate the Webmaker Component. Issues can be re-filed at https://github.com/mozillafoundation/mofo-devops/issues/new if required.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.