louislam/uptime-kuma

GameDig Discord Server Monitoring

Open

#4.304 aberto em 31 de dez. de 2023

Ver no 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

Guia do colaborador

Pilha de tecnologia
javascriptnodejs
Domain
backendobservability
Tipo Issue
bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 hours
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
active
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
needs investigation
Prerequisites
Understanding of Node.jsFamiliarity with Uptime Kuma's monitoring config
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
40
Direção de pesquisa
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.