Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GameDig Discord Server Monitoring #4304

Open
2 tasks done
dustyhansen opened this issue Dec 31, 2023 · 3 comments
Open
2 tasks done

GameDig Discord Server Monitoring #4304

dustyhansen opened this issue Dec 31, 2023 · 3 comments
Labels
area:monitor Everything related to monitors feature-request Request for new features to be added good first issue Good for newcomers type:enhance-existing feature wants to enhance existing monitor

Comments

@dustyhansen
Copy link

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

What hostname and port should I use for monitoring a GameDig Discord server? According to GameDig, you are supposed to use the GuildID but that doesn't work when I put it in hostname and I am forced to enter a port.

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

Docker

🌐 Browser

Opera GX

🐋 Docker Version

24.0.7

🟩 NodeJS Version

No response

@CommanderStorm CommanderStorm added bug Something isn't working area:monitor Everything related to monitors and removed help labels Dec 31, 2023
@CommanderStorm
Copy link
Collaborator

CommanderStorm commented Dec 31, 2023

Gamedig - discord should only allow configuring the guildId request field with the note from https://github.com/gamedig/node-gamedig/blob/master/GAMES_LIST.md#discord or should not be listed

Here are the respective lines that need changing in the first case:

<!-- TCP Port / Ping / DNS / Steam / MQTT / Radius / Tailscale Ping only -->
<div v-if="monitor.type === 'port' || monitor.type === 'ping' || monitor.type === 'dns' || monitor.type === 'steam' || monitor.type === 'gamedig' ||monitor.type === 'mqtt' || monitor.type === 'radius' || monitor.type === 'tailscale-ping'" class="my-3">
<label for="hostname" class="form-label">{{ $t("Hostname") }}</label>
<input id="hostname" v-model="monitor.hostname" type="text" class="form-control" :pattern="`${monitor.type === 'mqtt' ? mqttIpOrHostnameRegexPattern : ipOrHostnameRegexPattern}`" required>
</div>
<!-- Port -->
<!-- For TCP Port / Steam / MQTT / Radius Type -->
<div v-if="monitor.type === 'port' || monitor.type === 'steam' || monitor.type === 'gamedig' || monitor.type === 'mqtt' || monitor.type === 'radius'" class="my-3">
<label for="port" class="form-label">{{ $t("Port") }}</label>
<input id="port" v-model="monitor.port" type="number" class="form-control" required min="0" max="65535" step="1">
</div>

@CommanderStorm CommanderStorm added the good first issue Good for newcomers label Dec 31, 2023
@louislam louislam added feature-request Request for new features to be added and removed bug Something isn't working labels Jan 1, 2024
@dustyhansen
Copy link
Author

How is this a feature request when it is a feature that exists that doesn't work?

@CommanderStorm
Copy link
Collaborator

How something is classified does not super matter.
What matters is getting stuff better => here is our contribution guide

@CommanderStorm CommanderStorm added the type:enhance-existing feature wants to enhance existing monitor label Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:monitor Everything related to monitors feature-request Request for new features to be added good first issue Good for newcomers type:enhance-existing feature wants to enhance existing monitor
Projects
None yet
Development

No branches or pull requests

3 participants