louislam/uptime-kuma

GameDig Discord Server Monitoring

Open

#4.304 geöffnet am 31. Dez. 2023

Auf GitHub ansehen
 (7 Kommentare) (1 Reaktion) (0 zugewiesene Personen)JavaScript (86.760 Stars) (7.844 Forks)batch import
A:monitorfeature-requestgood first issuetype:enhance-existing

Beschreibung

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

Contributor Guide

Tech Stack
javascriptnodejs
Domain
backendobservability
Issue Type
bug
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
1-3 hours
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
active
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
needs investigation
Voraussetzungen
Understanding of Node.jsFamiliarity with Uptime Kuma's monitoring config
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
40
Research-Richtung
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.