louislam/uptime-kuma

GameDig Discord Server Monitoring

Open

#4,304 opened on Dec 31, 2023

View on GitHub
 (7 comments) (1 reaction) (0 assignees)JavaScript (7,844 forks)batch import
A:monitorfeature-requestgood first issuetype:enhance-existing

Repository metrics

Stars
 (86,760 stars)
PR merge metrics
 (Avg merge 6d 15h) (21 merged PRs in 30d)

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

Research direction
Review GameDig documentation for Discord server monitoring to find the correct hostname and port parameters; test with the GuildID as hostname and common ports.
Tech stack
javascriptnodejs
Domain
devops
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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.
Unclear
Prerequisites
Uptime Kuma basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70