PixelPerfectorandClaude Opus 4.8 e19dd43293 fix(notifications): use real server name in remote threshold alerts ...

Server CPU/Memory threshold notifications for remote servers always
showed "Server Name: Remote" instead of the actual server name, making
it impossible to tell which server triggered the alert when more than
one remote server is registered.

The remote branch of receiveNotification already fetches the matching
server row (looked up by its metrics token) but discarded it, hardcoding
ServerName to the literal "Remote". Use the fetched row's name instead,
falling back to "Remote" if it is somehow absent.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

2026-07-10 17:51:34 +03:00

..

api

Feat/tailwind v4 shadcn update (#4706)

2026-06-30 15:45:23 -06:00

dokploy

fix(notifications): use real server name in remote threshold alerts

2026-07-10 17:51:34 +03:00

monitoring

fix: enhance container metrics query to support wildcard matching for container names

2026-03-08 16:16:45 -06:00

schedules

Feat/tailwind v4 shadcn update (#4706)

2026-06-30 15:45:23 -06:00