louislam/uptime-kuma

GameDig Discord Server Monitoring

Open

#4 304 ouverte le 31 déc. 2023

Voir sur GitHub
 (7 commentaires) (1 réaction) (0 assignés)JavaScript (86 760 stars) (7 844 forks)batch import
A:monitorfeature-requestgood first issuetype:enhance-existing

Description

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

Guide contributeur

Stack technique
javascriptnodejs
Domaine
backendobservability
Type d'issue
bug
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
active
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
needs investigation
Prérequis
Understanding of Node.jsFamiliarity with Uptime Kuma's monitoring config
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
40
Direction de recherche
First, examine the Uptime Kuma source code to understand how GameDig monitoring is implemented (likely in the 'server/server.js' or a plugin). Check the GameDig library documentation to see if Discord servers require a specific query format (e.g., using GuildID as hostname with no port). Then, reproduce the issue by attempting to add a Discord monitor with a GuildID. If the problem is in the UI validation (requiring a port), consider modifying the validation logic or adding a note in the UI that for Discord, the GuildID goes in the hostname field without a port. If the issue is documentation, update the relevant help text or documentation file. Finally, create a pull request with the fix and reference this issue.