Closed stephen-soltesz closed 4 years ago
Currently there are two script-exporter configurations targeting the m-lab platform. One running in a VM using tc rules to limit aggregate bandwidth, and another running in GKE using ndt5-client -throttle to limit bandwidth.
ndt5-client -throttle
Over the last few days, the new script exporter identifies health nodes at least as good as the ndt_e2e.
This change promotes the new e2e script exporter using ndt5_client to be the default used by mlab-ns.
This change adds a dependency on the locate service because the ndt5_client uses monitoring access tokens issued by the locate service.
This change is
https://github.com/m-lab/dev-tracker/issues/574
stephen-soltesz
commented
4 years ago
Currently there are two script-exporter configurations targeting the m-lab platform. One running in a VM using tc rules to limit aggregate bandwidth, and another running in GKE using
ndt5-client -throttleto limit bandwidth.Over the last few days, the new script exporter identifies health nodes at least as good as the ndt_e2e.
This change promotes the new e2e script exporter using ndt5_client to be the default used by mlab-ns.
This change adds a dependency on the locate service because the ndt5_client uses monitoring access tokens issued by the locate service.
This change is