Sid Sun 0890660e01 Prepend hostname to notification message ... If multiple instances of uptime-kuma are deployed to cross-check each other and/or in different environments (say ipv4+ipv6 and ipv6 only), and only one or some of the instances fire notificationsm, it is tricky to figure out which specific environment is experiencing the outage. Explicitly setting unique hostnames and prepending it to the message will help in these scenarios. Signed-off-by: Sid Sun <sids@Sids-MacBook.local>		2025-05-09 08:43:10 +10:00
..
api_key.js	Added JSDoc to ESLint (#3529)	2023-08-11 15:46:41 +08:00
docker_host.js	Added JSDoc to ESLint (#3529)	2023-08-11 15:46:41 +08:00
group.js	Made sure that more of the async usages are awaited (#4574)	2024-03-15 15:02:55 +01:00
heartbeat.js	Feat: Retries persistence (#3814)	2023-11-24 18:11:36 +08:00
incident.js	Added JSDoc to ESLint (#3529)	2023-08-11 15:46:41 +08:00
maintenance.js	updated comments and ran linter on inferDuration	2024-07-15 17:04:16 -04:00
monitor.js	Prepend hostname to notification message	2025-05-09 08:43:10 +10:00
proxy.js	Added JSDoc to ESLint (#3529)	2023-08-11 15:46:41 +08:00
remote_browser.js	Feature: remote browser support (#3904)	2023-12-01 15:29:10 +08:00
status_page.js	feat: implement very crude and bare-bones RSS feed (#5047)	2024-09-03 13:51:34 +02:00
tag.js	Added JSDoc to ESLint (#3529)	2023-08-11 15:46:41 +08:00
user.js	Feat: Refresh login token for the client initiating password change (#4214)	2023-12-18 19:52:49 +08:00