Please setup config / reports for STAGE autopush-pypy stack

RESOLVED FIXED

Status

Cloud Services
Operations: Autopush
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: rpapa, Assigned: oremj)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

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:

[1]. Map a secondary URL on stage for this? 
     (i.e. autopush-pypy.stage.mozaws.net)  

[2]. 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
Assignee: nobody → oremj
Status: NEW → ASSIGNED
QA Contact: rpappalardo
(Assignee)

Comment 1

a year ago
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.
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
works great, thanks :oremj
Status: RESOLVED → VERIFIED
:oremj can you also enable Kibana reports for autopush-pypy STAGE?  We'll need this to troubleshoot connections being dropped.  thanks!
Status: VERIFIED → REOPENED
Flags: needinfo?(oremj)
Resolution: FIXED → ---
(Assignee)

Comment 4

a year ago
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.
Status: REOPENED → RESOLVED
Last Resolved: a year agoa year ago
Flags: needinfo?(oremj)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.