louislam/uptime-kuma

GameDig Discord Server Monitoring

Open

#4,304 创建于 2023年12月31日

在 GitHub 查看
 (7 评论) (1 反应) (0 负责人)JavaScript (86,760 star) (7,844 fork)batch import
A:monitorfeature-requestgood first issuetype:enhance-existing

描述

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

贡献者指南

技术栈
javascriptnodejs
领域
backendobservability
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Understanding of Node.jsFamiliarity with Uptime Kuma's monitoring config
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
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.