Closed
Bug 921170
Opened 11 years ago
Closed 11 years ago
Verify no more telemetry data is going to Bagheera, shut down relay code.
Categories
(Webtools Graveyard :: Telemetry Server, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mreid, Unassigned)
References
Details
We can check the ganglia graphs to make sure the telemetry submission rate goes to zero. Similarly, we can check the heka graphs on the new servers to make sure submission rate goes up to 100% of expected rate. We should also verify that data is making its way to the "incoming" bucket, being processed, and getting published. If everything checks out, shut down the "relay" infrastructure: - Log in to bagheera[1-4], kill replay consumer - Log in to mpt-vpn, kill tunnels - Log in to telemetry-node-server (ec2-54-245-195-188.us-west-2.compute.amazonaws.com), kill tunnels + relay servers
Reporter | ||
Comment 1•11 years ago
|
||
Incoming telemetry submission rate for Bagheera is now zero. Submission rate on the new servers seems normal, and incoming data is making its way to the production published data bucket. Relay infrastructure will be shut down presently.
Reporter | ||
Comment 2•11 years ago
|
||
Relays have been shut down.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•