louislam/uptime-kuma

GameDig Discord Server Monitoring

Open

#4304 opened on Dec 31, 2023

View on GitHub
 (7 comments) (1 reaction) (0 assignees)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

Contributor guide

Tech stack
javascriptnodejs
Domain
backendobservability
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Understanding of Node.jsFamiliarity with Uptime Kuma's monitoring config
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.