Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

Update heka configuration for awsbox #358

Merged
merged 1 commit into from Nov 27, 2013
Merged

Update heka configuration for awsbox #358

merged 1 commit into from Nov 27, 2013

Conversation

rfk
Copy link
Contributor

@rfk rfk commented Nov 27, 2013

This updates our scripted awsbox setup to latest heka release, and adds a bit better log/process management. Fixes #352 for fxa-auth-server.

@dannycoates r?

Once this is merged we need to:

  • copy similar logic into fxa-content-server
  • deploy api-accounts, accounts and accounts-latest with the changes (I already did accounts-latest as a test-run)

@rfk
Copy link
Contributor Author

rfk commented Nov 27, 2013

Holiday weekend so I'm just going to go ahead and merge this, we'll want it in place for next week.

rfk added a commit that referenced this pull request Nov 27, 2013
Update heka configuration for awsbox
@rfk rfk merged commit c334009 into master Nov 27, 2013
@jbonacci
Copy link

jbonacci commented Dec 5, 2013

See my notes here: mozilla/fxa-content-server#96
Now I am thinking a more general heka bug in fxa-deployment could work for both Dev stacks...

@dannycoates dannycoates deleted the rfk/update-dev-heka branch January 15, 2014 00:33
rfk pushed a commit that referenced this pull request Oct 24, 2018
Any requests that don't opt out of receiving the email will log a
warning.

Closes #358
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix heka logging on the Dev stacks
2 participants