Improve Telegram Notification for Server Restart

Open Beginner friendly
#3,589 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
backend, devops

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.

Description

enhancement
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

Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 43m
Merged PRs (30d)
72

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Dokploy/dokploy

All issues in Dokploy/dokploy

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.