1 Reply Latest reply on Jan 19, 2018 1:30 PM by jbiggley

    TCP Port Monitor component - Is it supported via the Windows agent?

    jbiggley

      I've been testing a few component monitors against some known-good servers this morning and I keep getting back the following response.

       

       

      TCP Port Monitor says that it is supported by the Linux agent but it does not appear to be supported by the Windows agent without the ability to tell the component to use the DNS name of the node.

       

      Any thoughts here?

        • Re: TCP Port Monitor component - Is it supported via the Windows agent?
          jbiggley

          So after some testing (and a recommendation from zackm) the answer to this question is YES -- the Windows agent does support a TCP component monitor, but you have to make a small change to the application monitor.

           

          When you build an application monitor, the preferred polling method is 'Agent'.  That is what forces the TCP component monitors to try and test against the node to which they are assigned using the IP 127.0.0.1.  In order to by-pass the agent and force the polling engine to do the testing, you need to flip the template from Agent to Agentless. 

           

          As a caveat, this will face ALL of the components within the template to use the polling engine, so plan carefully if you have an agent-polled node.  But you were already making distinct templates for the different application tiers and grouping component monitors into like templates, right?  Right?!?!

           

          1 of 1 people found this helpful