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

antenna: configure -dev environment

RESOLVED FIXED

Status

Cloud Services
Operations: Antenna
RESOLVED FIXED
11 months ago
10 months ago

People

(Reporter: willkg, Assigned: miles)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Antenna requires configuration in order to know how to access S3, statsd, etc.

This bug covers figuring out the correct configuration and doing whatever it is we do to set up the -dev environment to use that configuration.
I suspect we want something like this:

"""
# Statsd things
METRICS_CLASS=antenna.metrics.DogStatsdMetrics
STATSD_NAMESPACE=statsd-prefix

# BreakdpadSubmitterResource settings
CRASHSTORAGE_CLASS=antenna.ext.s3.crashstorage.S3CrashStorage

# S3CrashStorage and S3Connection settings
CRASHSTORAGE_BUCKET_NAME=bucket-name
CRASHSTORAGE_REGION=region-name
"""

where:

1. "statsd-prefix" is replaced with whatever prefix is appropriate
2. "bucket-name" is replaced with the bucket name
3. "region-name" is replaced with the region the bucket is in

Theoretically, that will default to statsd on localhost:8125 and use the IAM credentials for the EC2 node that it's on for the S3 bucket.
(Assignee)

Comment 2

11 months ago
I added the env variables to the Docker environment here: https://github.com/mozilla-services/cloudops-deployment/commit/9d952ebb8c89c91129a514cd7669cd1bb4624cff

STATSD_NAMESPACE is set to "antenna"
CRASHSTORAGE_BUCKET_NAM is set to "crashstats.antenna.{dev|stage|prod}"
(Assignee)

Comment 3

10 months ago
I believe this is complete and can be closed. Correct?
Flags: needinfo?(willkg)
Mmm... Yeah--let's close this out. If we discover any additional configuration changes that need to happen, we can do that in new bugs.

Thanks, Miles!
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Flags: needinfo?(willkg)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.