Canmove, confirm
6,438
edits
Changes
→ELB Logs
Changes made to Rules, Scheduled Rule Changes, Permissions, or the read-only flag of a Release will send e-mail notification to the [https://groups.google.com/a/mozilla.com/forum/#!forum/balrog-db-changes balrog-db-changes mailing list]. This serves us an alert system - if we see changes made that we weren't expecting, we can go investigate them.
== Nginx ELB Logs =='''NOTE: ''' These instructions were written before [https://aws.amazon.com/blogs/aws/amazon-athena-interactive-sql-queries-for-data-in-amazon-s3/ Amazon Athena existed]. The nginx next time we need to do such analysis, it's probably worth giving it a try. The ELB logs for the public-facing application are replicated to the '''balrog-us-west-2-elb-logs''' S3 bucket, located in us-west-2. Logs are rotated very quickly, and we end up with tens of thousands of separate files each day. Because of this, and the fact that S3 has a lot of overhead per-file, it can be tricky to do analysis on them. You're unlikely to be able to download the logs locally in any reasonable amount of time (ie, less than a day), but mounting them on an EC2 instance in us-west-2 should provide you with reasonably quick access. Here's an example:
* Launch EC2 instance (you probably a compute-optimized one, and at least 100GB of storage).
* Generate an access token for your CloudOps AWS account. If you don't have a CloudOps AWS account, talk to Ben Hearsum or Bensong Wong. Put the token in a plaintext file somewher on the instance.
