milki

Yes, this currently requires manual database changes. We will need to find a better way to handle daylight savings time changes.

> Would this be used in order to disable metrics if the sidecar doesn't exist? If so I don't really think we want to go that direction, although I could...

The difference between uwsgi metrics and gunicorn metrics is pull versus push. uwsgi metrics can be served directly by uwsgi whereas gunicorn must push metrics. In order to push metrics,...

An alternative workaround would be to keep the status quo with statsd always sending metrics and *strongly* suggesting autoscaling should be enabled. This would be compatible with moving the statsd-exporter.

Alternatively, making subscriptions active/inactive would be sufficient.

I'd be interested to see what you have. How do you deal with cases in which users forget to opt-out or want to opt-out for an extended period of time...

Given that our current userbase is in the opt-in flow, we don't think it would be great to switch everyone to the opt-out flow. We definitely want to have the...

Turns out, an old TODO was made for this issue: https://github.com/Yelp/beans/blob/fda948f38f4ce2bc789f4c4bfc63b3f40fbf302d/api/yelp_beans/send_email.py#L174 Given now that workforces are now scattered across the globe, this is an important quality of life bug to...

The meeting request email would be the first spike. And in this case, there were no match emails.  With categories, we could see...