We'd like to begin loadtesting the autopush-pypy stage, but leave the current (cpython) autopush in place so we can test them side-by-side. :oremj, can you please setup the following: . Map a secondary URL on stage for this? (i.e. autopush-pypy.stage.mozaws.net) . Create a separate report on datadog for the autopush-pypy STAGE stack NOTE: I assume a separate report won't be necessary for PROD because by the time we've properly tested (and decide to push) the new pypy stage it will simply replace the current stack @: push.services.mozilla.com
All set. You can view data for this stack by switching the "stack" variable, in datadog, to autopush-pypy. env should be prod and app should be autopush.
works great, thanks :oremj
:oremj can you also enable Kibana reports for autopush-pypy STAGE? We'll need this to troubleshoot connections being dropped. thanks!
relud fixed heka and the pypy and non-pypy are back at https://kibana.shared.us-east-1.stage.mozaws.net/index.html#/dashboard/file/autopush.json to separate pypy from non-pypy we would need to add a field in the app. It should be fairly obvious which is which are which.