uptime-kuma: Discord notification failing with Docker monitor

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn’t find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

Using docker monitor in conjunction with discord notifications results in error:

2022-12-21T09:55:44.132Z [MONITOR] ERROR: Cannot send notification to BCS INC
Error: Error: AxiosError: Request failed with status code 400 {"embeds":["0"]}
    at Discord.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
    at Discord.send (/app/server/notification-providers/discord.js:116:18)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Function.sendNotification (/app/server/model/monitor.js:939:21)
    at async beat (/app/server/model/monitor.js:615:25)
    at async Timeout.safeBeat [as _onTimeout] (/app/server/model/monitor.js:658:17)

Most likely cause is undefined value for Failing variable (which I assume is passed on to the Discord)

2022-12-21T09:55:23.928Z [MONITOR] WARN: Monitor #16 'BOT | Docker': Failing: undefined | Interval: 20 seconds | Type: docker | Down Count: 4 | Resend Interval: 5

Notification when container goes back UP works, so this seems to be strictly something with DOWN notifications.

👟 Reproduction steps

1. Monitor Docker container with Discord notifications enabled
2. Shut down container
3. Check UptimeKuma logs

👀 Expected behavior

A Discord message to pop-up once notify gets triggered

😓 Actual Behavior

Errors mentioned above in logs

🐻 Uptime-Kuma Version

1.18.5

💻 Operating System and Arch

Debian 10

🌐 Browser

Google Chrome 108.0.5359.124

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response