Generic TCP Tests (via RegEx)

[michaelkrieger]

⚠️ Please verify that this feature request has NOT been suggested before.

• I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

Generic / Custom TCP tests via regular expressions. The ability to connect to a port, send some data, and then evaluate the result (and maybe even with a timeout to ensure it's in a timely manner) would be helpful for services not supported by the app or which are custom in nature.

✔️ Solution

Using another monitoring, I have some services similar to this:

Service TCP/Submission {
    port: 587
    expect: ^220
    readhow: banner
}
Service TCP/webtest {
    port: 80
    send: HEAD / HTTP/1.0\r\n\r\n
    expect: HTTP
    readhow: toeof
}

❓ Alternatives

The documentation of that monitoring system describes these parameters as follows:

send: data to send once connected. This needs to be specified. If nothing is specified, nothing will be sent to the remote server
expect: a regular expression that needs to match the data received from the remote server. This needs to be specified. If nothing is specified, success or failure is determined by whether or not we received any data at all
readhow: This needs to be specified. How much data should we try to read? toeof indicates read until the remote end closes the connection. banner indicates we only want to read a banner. once indicates to use whatever data is returned in the first read(). This parameter only applies to TCP not UDP.

This is a generic TCP monitoring, which would not only be helpful, but also allow for the easy evaluation of any custom services that aren't easily added to the app.

📝 Additional Context

No response

[jordantrizz]

A good example. If you want to monitor if the SSH service is functioning, the port might be open but the service banner isn't being returned.

SSH-2.0-OpenSSH_7.4