0xfurai / 0xfurai/peekaping

Ping monitor doesn't report it is down for minutes

Abierto
#157 4 comentarios 1 reacción 0 asignados Ver en GitHub
to-triage
Lenguaje dominante
Go
Estrellas
1.2k
Forks
69
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**Describe the bug**
Adding a Ping monitor with default 20 seconds and 1 retry doesn't report as down when the device goes offline (turned off or Wifi off) in a timely matter.

**Database**
- sqlite

**To Reproduce**
Steps to reproduce the behavior:
1. Add ping monitor
2. Turn off monitor on that device (or unplug)
3. Wait for a period of time (longer than timeout and retry period).
4. Monitor will still report device is up

**Expected behavior**
When device isn't reachable, it shows as down straight away (as per interval time and reties) and alerts using notification channel immediately

**Screenshots**
Screenshots at multiple time periods showing comparison to Uptime Kuma

Image

Image

**Server (please complete the following information):**
- Ubuntu Server 22.04.5 LTS
- Docker version 28.0.4, build b8034c0
- Pi 4

**Desktop (please complete the following information):**
- Mac OS
- Safari
- 18.6

**Additional context**
I'm using a ChatGPT single Docker Compose file instead of the default .env setup. See below

```
services:
peekaping:
image: 0xfurai/peekaping-bundle-sqlite:latest
container_name: peekaping-bundle-sqlite
restart: unless-stopped
ports:
- "8383:8383"
environment:
DB_TYPE: sqlite
DB_NAME: /app/data/peekaping.db
# Optional (uncomment if you want):
# MODE: prod
TZ: Pacific/Auckland
# CLIENT_URL: "http://localhost:8383"
volumes:
- ./.data/sqlite:/app/data
- ./.data/logs:/var/log/supervisor
```

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

The ping monitor logic is likely in the backend service code, possibly in a file like `internal/monitor/ping.go` or similar. Start by looking for the ping check implementation and the retry/timeout logic. The issue suggests the monitor does not update status correctly after a failure; examine how status transitions are handled and logged. Check the database schema for monitor status fields and the alerting logic to see where the delay occurs. Reproduce the bug locally using the provided docker-compose setup to verify the behavior.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
docker, docker-compose, go, sqlite
Área
backend
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bien especificado
Aptitud para principiantes
45/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.