tree: b15e59ae04157dd9ccd9bc75377bfe5a6a116263 [path history] [tgz]
  1. docker_build.sh
  2. Dockerfile
  3. monitoring_proxy.sh
  4. monitoring_proxy_go_containers.yaml
  5. monitoring_proxy_go_containers_prod.yaml
  6. README.md
  7. setup.sh
docker/monitoring_proxy_go/README.md

This version of the proxy is a proof of concept, and is designed to work with chrome-infra-loadtest.appspot.com.

The clients would push directly to PubSub using patched ts_mon library, and a thin Go client running on a GCE VM with a static (whitelisted) IP will poll the subscription and forward data to the final endpoint.

Build the container:

  cd go
  ./install-deps.sh # Need to run only once, to init .verdor dir.
  source env.sh     # Will go away once moved to infra(_internal).

  go build src/infra_experimental/services/monitoring_proxy
  cp monitoring_proxy ../docker/monitoring_proxy_go
  cd ../docker/monitoring_proxy_go
  ./docker_build.sh

Update the manifest file with the new image tag, as the script tells you. Then:

  ./setup.sh proxy1
  ./setup.sh proxy2
  ./setup.sh proxy3

Deploy the new container, or revert the previously deployed change:

  • Update the image hash in monitoring_proxy_go_containers.yaml
  • ./setup.sh proxy1 # This will respin the VM with the new container.

To Do

  • Make monitoring_proxy.sh read the credentials from the metadata server on GCE, write to a file and give it to the executable.