{"id":4244,"date":"2013-09-05T10:26:34","date_gmt":"2013-09-05T14:26:34","guid":{"rendered":"http:\/\/www.webperformance.com\/load-testing-tools\/blog\/?p=4244"},"modified":"2023-06-29T11:23:09","modified_gmt":"2023-06-29T15:23:09","slug":"monitoring-server-performance-through-firewalls-now-easier-with-proxy-tunnels-in-load-tester-5-4","status":"publish","type":"post","link":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/2013\/09\/monitoring-server-performance-through-firewalls-now-easier-with-proxy-tunnels-in-load-tester-5-4\/","title":{"rendered":"Monitoring Server Performance through Firewalls now easier with Proxy Tunnels in Load Tester 5.4"},"content":{"rendered":"

So you’re getting setup to run your next test. You’ve installed our server monitor agent on each server, and are ready to start collecting server data while the test is running. However, there’s a snag: your workstation is on a different network from the servers, and you’re not able to open up the firewall on the servers to forward traffic.<\/p>\n

Enter Load Tester 5.4. Load Tester 5.4 supports connecting to server agents through a SOCKS proxy. This means that if you can get a SSH session open to even just one server behind the firewall, you can now monitor your servers.<\/p>\n

    \n
  1. Start by getting a SSH client which supports tunneling. For our example, we’ll use PuTTY<\/a>, but other clients may have similar support.<\/li>\n
  2. Open PuTTY, and enter the hostname of the SSH server on the Session Tab<\/li>\n
  3. Select Connection -> SSH -> Tunnels
    \n\"putty-tunnel2\"<\/li>\n
  4. Enter a source port number (we’ve arbitrarily selected 5000).<\/li>\n
  5. Make sure the Destination is set to “Dynamic<\/strong>“, and press “Add<\/strong>“.<\/li>\n
  6. Press “Open”, and login as normal.<\/li>\n
  7. Minimize, but do not close PuTTY<\/li>\n
  8. Open Load Tester, and select the Servers View<\/li>\n
  9. Press Add<\/strong>
    \n\"add-server\"<\/li>\n
  10. In the Hostname, enter the internal<\/em> IP address of the server to monitor<\/li>\n
  11. Select Advanced<\/strong><\/li>\n
  12. Select “Connect through SOCKS proxy”, and enter Hostname: “localhost”, Port: 5000 (the same port used in step #4).<\/li>\n
  13. Press OK, and Load Tester will now connect to your server, using PuTTY as a tunnel, so you can receive live server performance data!
    \n\"servers-view\"<\/li>\n<\/ol>\n

    Note, however: care should be taken in considering which servers to use for SSH tunnels. For example, if the “tunnel” server should go down, or become saturated with bandwidth as a result of the test, any server agent connections will stop updating until the issue is corrected. However, you will still be able to collect the complete data from the servers after the test completes.<\/p>\n

    We hope this feature will make server monitoring easier for users in the future. If you have any difficulty or questions, or friendly support staff will be more than happy to answer your concerns!<\/p>\n","protected":false},"excerpt":{"rendered":"

    So you’re getting setup to run your next test. You’ve installed our server monitor agent on each server, and are ready to start collecting server data while the test is running. However, there’s a snag: your workstation is on a different network from the servers, and you’re not able to open up the firewall on the servers to forward traffic.
    \nEnter Load Tester 5.4. Load Tester 5.4 supports connecting to server agents through a SOCKS proxy. This means that if you can get a SSH session open to even just one server behind the firewall, you can now monitor your servers.<\/p>\n

    Start … Continue reading »<\/a><\/p>\n","protected":false},"author":12,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[42],"tags":[178,49,180,176,179,177],"class_list":["post-4244","post","type-post","status-publish","format-standard","hentry","category-load-tester-software","tag-firewall","tag-load-tester","tag-monitoring","tag-proxy","tag-server","tag-socks"],"_links":{"self":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/4244","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/comments?post=4244"}],"version-history":[{"count":22,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/4244\/revisions"}],"predecessor-version":[{"id":6350,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/4244\/revisions\/6350"}],"wp:attachment":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/media?parent=4244"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/categories?post=4244"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/tags?post=4244"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}