Feature: Add TCP ports to monitor

[kool2zero]

Is your feature request related to a problem? Please describe.
Currently, we are able to ping a host, but an app might be served on a specific port and not necessarily over HTTP.

Describe the solution you'd like
Adding Port monitor would be an additional check to see if the application is up.

Describe alternatives you've considered
Creating an http request node-red flow to check the port and then use the API in Kener to validate.

[rajnandan1]

Can you please describe what specifically you want to monitor. Please give an example. I am not able to understand.

[kool2zero]

Hi,
Let's say I have an application that listens for connections on a specific port (let's say 3000). I want to be able to check that port 3000 is open an accepting connections.

In PowerShell, I would do something like this:

$tcpConnection = Test-NetConnection -ComputerName $ComputerName -Port $Port
            if ($tcpConnection.TcpTestSucceeded) {
                Write-Output "Port $Port is open on $ComputerName."
                return
            } else {
                Write-Output "Port $Port is not open on $ComputerName. "
            }

[Yavzkesta]

I would also like a feature like this. Since I have several services on different ports, I want to be able to monitor an IP:port combination.

ex:
nc -zvn X.X.X.X 8080
(UNKNOWN) [X.X.X.X] 8080 (http-alt) open

nc -zvn X.X.X.X 8081
(UNKNOWN) [X.X.X.X] 8081 (tproxy) : Connection refused

[rajnandan1]

It will be release as part of 3.0.9. ETA would be 7th Feb 2025