Improve Telegram Notification for Server Restart
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Currently, when a Dokploy server restarts, the Telegram bot sends a generic notification:
✅ Dokploy Server Restarted
Date: Feb 4, 2026
Time: 4:09:13 AM
This notification lacks important context — which specific server was restarted. Users with multiple servers or projects cannot immediately identify which instance was affected.
Describe the solution you'd like
Enhance the Telegram notification format for server restarts to include server identification, similar to existing build success notifications:
Current build success notification (good example):
✅ Build Success
Project: project-name
Application: front
Environment: production
Type: application
Date: Jan 14, 2026
Time: 12:57:38 PM
Proposed server restart notification:
✅ Server Restarted
Server: server-name-or-identifier
Date: Feb 4, 2026
Time: 4:09:13 AM
Describe alternatives you've considered
Additional information that could be included:
- Server hostname or identifier
- Server IP address (or last octet for privacy)
- Restart reason (manual, crash, update, etc.)
- Uptime before restart (optional)
Additional context
No response
Will you send a PR to implement it?
Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the code that sends the current Telegram server-restart notification and compare it with the existing build-success notification format described in the issue. Update the restart message to identify the affected server, then verify that a restart produces the expected server, date, and time fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100