starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 22:25:59 +03:00

[GH-ISSUE #2493] MQTT-support for alerts. Proof-of-concept implemented. Feedback requested #1832

New issue

Open

opened 2026-02-27 02:59:16 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 02:59:16 +03:00

Owner

Originally created by @insensitiveclod on GitHub (Aug 29, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2493

TLDR:

I have implemented a method to get LGSM alerts to be distributed via the MQTT protocol.
I am looking for feedback on it , review the implementation AND on guidance on how to get it prepped for inclusion into the base LGSM package.

A proof of concept is in 'insensitiveclod/LinuxGSM'

Long version:

I have implemented:
alert_mqtt.sh

And altered:
alert_sh (to know what to do)
core_functions.sh (to know about it)
core_dl.sh (to define mqttpubpath... Is possibly not the right place ?)

Also, an example config has been made for rust:
rustserver/_default.cfg

Since I only started using LGSM about a month ago, and I just checked out the source 4 days ago, I dont know if there's particular requirements/ideas that I am missing in my implementation.

I aim to re-write json-format of the alert_mqtt.sh message somewhat to more correspond to something that'll be easily parseable by something like NodeRed
I am thinking of doing this with a 'mqttjsontemplate' config-param that'll allow formatting things from the config-file, as it would be quite a pain to have to edit alert_mqtt.sh for most users.

The config currently knows about:
mqttalert on/off
mqtthost server-name/ip
mqttport service-port
mqttuser user to login with (anonymous-user support coming)
mqttpassword password for user (see above)
mqtttopic mqtt 'topic' name.

The mqtttopic is currently 'fixed'. That is, '/lgsm/rustserver' for the rust-server example.
I am thinking of changing it to "mqtttopicbase" instead, so the full topic of any alert will be in the form of /lgsm/rustserver/$instancename/
If you know how MQTT works, this will mean you can subscribe to /lgsm/rustserver/# and get messages from ALL instances; of /lgsm/rustserver/rustserver1 for the 'rustserver1' instance , only.

Comments very welcome.
Keen to have this be available for anyone/everyone.

Originally created by @insensitiveclod on GitHub (Aug 29, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2493 TLDR: I have implemented a method to get LGSM alerts to be distributed via the MQTT protocol. I am looking for feedback on it , review the implementation AND on guidance on how to get it prepped for inclusion into the base LGSM package. A proof of concept is in '[insensitiveclod/LinuxGSM](https://github.com/insensitiveclod/LinuxGSM)' Long version: I have implemented: alert_mqtt.sh And altered: alert_sh (to know what to do) core_functions.sh (to know about it) core_dl.sh (to define mqttpubpath... Is possibly not the right place ?) Also, an example config has been made for rust: rustserver/_default.cfg Since I only started using LGSM about a month ago, and I just checked out the source 4 days ago, I dont know if there's particular requirements/ideas that I am missing in my implementation. I aim to re-write json-format of the alert_mqtt.sh message somewhat to more correspond to something that'll be easily parseable by something like NodeRed I am thinking of doing this with a 'mqttjsontemplate' config-param that'll allow formatting things from the config-file, as it would be quite a pain to have to edit alert_mqtt.sh for most users. The config currently knows about: mqttalert on/off mqtthost server-name/ip mqttport service-port mqttuser user to login with (anonymous-user support coming) mqttpassword password for user (see above) mqtttopic mqtt 'topic' name. The mqtttopic is currently 'fixed'. That is, '/lgsm/rustserver' for the rust-server example. I am thinking of changing it to "mqtttopicbase" instead, so the full topic of any alert will be in the form of /lgsm/rustserver/$instancename/ If you know how MQTT works, this will mean you can subscribe to /lgsm/rustserver/# and get messages from ALL instances; of /lgsm/rustserver/rustserver1 for the 'rustserver1' instance , only. Comments very welcome. Keen to have this be available for anyone/everyone.

kerem added the

type: feature

info: alerts

labels

2026-02-27 02:59:16 +03:00

kerem commented

2026-02-27 02:59:17 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Aug 29, 2019):

Issue-Label Bot is automatically applying the label type: feature request to this issue, with a confidence of 0.81. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Aug 29, 2019): Issue-Label Bot is automatically applying the label `type: feature request` to this issue, with a confidence of 0.81. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 02:59:17 +03:00

Author

Owner

@BrutalBirdie commented on GitHub (Aug 30, 2019):

I am looking for feedback on it

IMHO
MQTT is a nice addition. Some people won't know what do with it.
I like it! With MQTT enabled for LGSM I can add my Server(s) to my SmartHome via. openHAB.
If I get time I will test and check your code.

@BrutalBirdie commented on GitHub (Aug 30, 2019): > I am looking for feedback on it IMHO MQTT is a nice addition. Some people won't know what do with it. I like it! With MQTT enabled for LGSM I can add my Server(s) to my SmartHome via. openHAB. If I get time I will test and check your code.

kerem commented

2026-02-27 02:59:17 +03:00

Author

Owner

@insensitiveclod commented on GitHub (Sep 9, 2019):

Cheers, thanks for your response.

The nice thing is that it integrates with quite a few services 'under the hood' as well.
A lot of the Internet of Things infrastructure has chosen MQTT as it's default method of communication. ITTT, TheThingsNetwork (Lorawan), etc.. So that makes it nice to be able to recieve these kinds of game-server messages on your devices OR remix them in other ways.

Lemme know what changes/modifications might be useful to have it be ready for inclusion or a pull-request.

@insensitiveclod commented on GitHub (Sep 9, 2019): Cheers, thanks for your response. The nice thing is that it integrates with quite a few services 'under the hood' as well. A lot of the Internet of Things infrastructure has chosen MQTT as it's default method of communication. ITTT, TheThingsNetwork (Lorawan), etc.. So that makes it nice to be able to recieve these kinds of game-server messages on your devices OR remix them in other ways. Lemme know what changes/modifications might be useful to have it be ready for inclusion or a pull-request.

kerem commented

2026-02-27 02:59:17 +03:00

Author

Owner

@noldona commented on GitHub (Jul 11, 2022):

+1 for this feature. I use Home Assistant would would love to be able to automatically report the server's status to it.

@noldona commented on GitHub (Jul 11, 2022): +1 for this feature. I use Home Assistant would would love to be able to automatically report the server's status to it.