starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Check Telnet port for correct response #989

New issue

Open

opened 2026-02-28 02:06:22 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-28 02:06:22 -05:00

Owner

Originally created by @HolgerAusB on GitHub (Apr 17, 2022).

⚠️ 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

Inspired by #9 and the wish of @choffmeister of monitoring a Teamspeak server, I would sugguest to implement a telnet monitor. Teamspeak servers have a telnet interface, standardport is 10011.

If Kuma would support monitoring via telnet protocol, that would be great. In addition, we should be able to specify a comparison pattern that is compared with the response of the server.

Maybe the expect-package is helpful?

✔️ Solution

call a server via telnet port an compare the answer with a pattern

❓ Alternatives

One could use a variant of my script (via cron job) to set an mqtt-topic if telnet does not show the greeting-message. And then use the new mqtt-Monitor in Kuma (currently in pre-release 1.15.0-beta.0).

📝 Additional Context

No response

Originally created by @HolgerAusB on GitHub (Apr 17, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Monitor ### 🔖 Feature description Inspired by #9 and the wish of @choffmeister of monitoring a Teamspeak server, I would sugguest to implement a `telnet monitor`. Teamspeak servers have a telnet interface, standardport is 10011. If Kuma would support monitoring via telnet protocol, that would be great. In addition, we should be able to specify a comparison pattern that is compared with the response of the server. Maybe the [expect-package](https://en.wikipedia.org/wiki/Expect) is helpful? ### ✔️ Solution call a server via telnet port an compare the answer with a pattern ### ❓ Alternatives One could use a variant [of my script](https://github.com/HolgerAusB/Teamspeak3-to-MQTT) (via cron job) to set an mqtt-topic if telnet does not show the greeting-message. And then use the new mqtt-Monitor in Kuma (currently in pre-release 1.15.0-beta.0). ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:monitor

labels

2026-02-28 02:06:22 -05:00

deekerman commented

2026-02-28 02:06:26 -05:00

Author

Owner

@Computroniks commented on GitHub (Apr 17, 2022):

This would be a nice feature to have but I am not sure about its applications other than for TeamSpeak as you suggest. I am also not sure how widely telnet is used as a monitoring system anymore due to it being overtaken by systems such as SSH in terms of security. Do you perhaps have any other use cases for this monitor type?

@Computroniks commented on GitHub (Apr 17, 2022): This would be a nice feature to have but I am not sure about its applications other than for TeamSpeak as you suggest. I am also not sure how widely telnet is used as a monitoring system anymore due to it being overtaken by systems such as SSH in terms of security. Do you perhaps have any other use cases for this monitor type?

deekerman commented

2026-02-28 02:06:26 -05:00

Author

Owner

@HolgerAusB commented on GitHub (Apr 17, 2022):

I don't know about other systems. But as it is a low security protocol, I think it could be easy to build a monitor. I might be wrong about that point.

try a connection to telnet server
do we get a connection?
do we get a response / greeting message / (login) prompt and does this message match with a pattern?
in this simple case, no need for credentials to send via telnet

maybe same monitor works for SSH or similar protocols too?

@HolgerAusB commented on GitHub (Apr 17, 2022): I don't know about other systems. But as it is a low security protocol, I think it could be easy to build a monitor. I might be wrong about that point. - try a connection to telnet server - do we get a connection? - do we get a response / greeting message / (login) prompt and does this message match with a pattern? - in this simple case, no need for credentials to send via telnet maybe same monitor works for SSH or similar protocols too?

deekerman commented

2026-02-28 02:06:26 -05:00

Author

Owner

@augustgerro commented on GitHub (Sep 2, 2022):

Telnet us totally unsecured protocols, many companies disabled it long time ago.
It seems to me that monitoring for SSH is a higher priority

@augustgerro commented on GitHub (Sep 2, 2022): Telnet us totally unsecured protocols, many companies disabled it long time ago. It seems to me that monitoring for SSH is a higher priority

deekerman commented

2026-02-28 02:06:26 -05:00

Author

Owner

@weedy commented on GitHub (Oct 19, 2025):

I work with appliances in my day to day. And while the TCP monitor lets me know something exists, the HTTP monitor is where I get real work done.

And by extension where I would love a telnet/nc monitor.
Even just today

# telnet localhost 3493
Connected to localhost
VER
Network UPS Tools upsd

I'd love to run this right in kuma instead of having to do silly things outside of kuma and push it back with the API.

@weedy commented on GitHub (Oct 19, 2025): I work with appliances in my day to day. And while the TCP monitor lets me know something exists, the HTTP monitor is where I get real work done. And by extension where I would love a telnet/nc monitor. Even just today ``` # telnet localhost 3493 Connected to localhost VER Network UPS Tools upsd ``` I'd love to run this right in kuma instead of having to do silly things outside of kuma and push it back with the API.