don't need to scrape lines with 'tcp' in them any more from h2o stdout (tcp_active was triggering an info scrape when cloud status json was dumped) any tcp related messaging should have WARN or INFO or exception, so we should see it still.
don't need to scrape lines with 'tcp' in them any more from h2o stdout
(tcp_active was triggering an info scrape when cloud status json was dumped)
any tcp related messaging should have WARN or INFO or exception, so we should see it still.

h2oai/h2o-2,vbelakov/h2o,h2oai/h2o,calvingit21/h2o-2,elkingtonmcb/h2o-2,elkingtonmcb/h2o-2,rowhit/h2o-2,vbelakov/h2o,eg-zhang/h2o-2,calvingit21/h2o-2,vbelakov/h2o,111t8e/h2o-2,eg-zhang/h2o-2,eg-zhang/h2o-2,100star/h2o,100star/h2o,rowhit/h2o-2,111t8e/h2o-2,vbelakov/h2o,elkingtonmcb/h2o-2,rowhit/h2o-2,111t8e/h2o-2,calvingit21/h2o-2,h2oai/h2o-2,h2oai/h2o,100star/h2o,vbelakov/h2o,h2oai/h2o-2,111t8e/h2o-2,rowhit/h2o-2,h2oai/h2o,h2oai/h2o-2,rowhit/h2o-2,vbelakov/h2o,100star/h2o,h2oai/h2o,eg-zhang/h2o-2,elkingtonmcb/h2o-2,h2oai/h2o,111t8e/h2o-2,elkingtonmcb/h2o-2,eg-zhang/h2o-2,h2oai/h2o,vbelakov/h2o,calvingit21/h2o-2,100star/h2o,eg-zhang/h2o-2,h2oai/h2o,h2oai/h2o,rowhit/h2o-2,rowhit/h2o-2,elkingtonmcb/h2o-2,h2oai/h2o-2,elkingtonmcb/h2o-2,100star/h2o,rowhit/h2o-2,eg-zhang/h2o-2,h2oai/h2o-2,calvingit21/h2o-2,elkingtonmcb/h2o-2,h2oai/h2o,h2oai/h2o-2,calvingit21/h2o-2,vbelakov/h2o,100star/h2o,elkingtonmcb/h2o-2,h2oai/h2o-2,eg-zhang/h2o-2,h2oai/h2o,111t8e/h2o-2,elkingtonmcb/h2o-2,100star/h2o,calvingit21/h2o-2,111t8e/h2o-2,rowhit/h2o-2,vbelakov/h2o,eg-zhang/h2o-2,calvingit21/h2o-2,vbelakov/h2o,calvingit21/h2o-2,h2oai/h2o-2,111t8e/h2o-2,111t8e/h2o-2,100star/h2o,h2oai/h2o-2,calvingit21/h2o-2,rowhit/h2o-2,eg-zhang/h2o-2,111t8e/h2o-2