Skip to content

feat: Implement comprehensive powerful multi-channel notification system with templating#129

Merged
tolaleng merged 45 commits intomainfrom
develop
Aug 14, 2025
Merged

feat: Implement comprehensive powerful multi-channel notification system with templating#129
tolaleng merged 45 commits intomainfrom
develop

Conversation

@tolaleng
Copy link
Copy Markdown
Member

  • Add robust notification system supporting 7+ communication channels with intelligent message templating, resource monitoring, and SSL certificate alerts. Notification Channels: (Telegram, Discord, Slack, Signal, Email, Google Chat, Webhooks).
  • This notification system provides enterprise-grade alerting capabilities with extensive customization options and multi-channel redundancy for critical service monitoring.
  • Chinese language added
  • Server and Service Table row clickable to detail page.
  • Implement pagination for the SSL dashboard table
  • Server Agent (RPM, Docker container, and general binary package)
  • Improve Uptime Service and Server connection update based on status and notification.
  • Improve SSL perform the initial check automatically after creation
  • Backend Rate limiting and abuse protection

gnsworks and others added 30 commits July 14, 2025 20:32
- Disable log console output in file to prevent logs from being printed to the console.
- Reduce verbose logging in install-regional-agent.sh to provide a more minimal output while retaining all core functionality.
- When adding a new SSL certificate, initialize with the current time. This ensures that the SSL check is triggered shortly after the certificate is added to the monitoring system.
- Update the Notification Settings dashboard to allow users to select multiple notification channels for alerts.
- Add webhook to notification channels: Add webhook as a selectable option in the notification channel type dropdown.
- Implement template type selection in the Add Template dialog. Based on the selected type.
- Add webhook notification channel configuration. Allow users to define custom payload structures for webhook notifications.
- The Alert Template field in the Service dialog will now correctly fetch data from service_notification_templates
- Remove the separate "Update Thresholds" button and integrate its functionality into the main "Update Server" button.
…it Domain Form

- Add multi-select for notification channels and an alert template field to the Add/Edit SSL Certificate dialog
- Added Google Chat  as a new channel type option in the Notification Channel
- Add Google Chat tab to notifications
- Fix: Ensure Google Chat and Email save record to PB
- Display icons for each notification channel type in the dialog and dropdown.
- Remove the QuickActionsDialog component and its associated file from the dashboard.
- Add a new tab for "Server Threshold" to the Alert Templates dashboard, to allow users to manage server threshold configurations.
- Wrap the Subject Alternative Names (SANs) in the SSL detail dialog to ensure they break onto new lines when there are multiple entries, improving readability.
Update Japanese translation
- Translate untranslated text in the SSL Certificate Details dialog. The following keys have been translated:
- certificateDetails
- subjectAlternativeNames
- monitoringConfiguration
- technicalInformation
- This fix ensures that when the notification status is enabled. Resolves the issue where the status was incorrectly shown as false in PB.
- This fix ensures that when the notification status is toggled off, notification_channels, threshold_id, and template_id are no longer cleared or emptied.
- Add new fields for restore messages to the Server Template Dialog to match the DB schema.
- Adds support for new placeholders in the Service Uptime Monitoring alert templates. The following placeholders are now available:
-- ${ip_host}: The IP address or hostname of the service.
-- ${service_type}: The type of the service (e.g., HTTP, PING, TCP, DNS).
-- ${port}: The port the service is running on.
-- ${domain}: The domain name of the service.
-- ${region_agent}: The regional agent monitoring the service.
tolaleng and others added 15 commits August 12, 2025 22:23
- Improve Telegram notification messages for uptime services by adding support for new placeholders.
- Add support for the `${error_message}` placeholder in uptime service notifications
- Add simplified Chinese translation files
- Add the Simplified Chinese option in the language selection
- Update the translation index to support Simplified Chinese
- Added the "german" and "japanese" fields to the common.ts file
- Add a README_zhcn.md file in the docs directory, which contains the Chinese documentation content.
- Add a link to the Chinese language option in README.md and READMEs in other languages
feat(translations): Add Simplified Chinese translation
- Allowing notifications to be re-enabled correctly without losing previously configured
- This change ensures that users can see and manage their existing SSL configurations.
- Add an input field for SMTP password in the "Add Notification Channel" dialog. This field will be used for SMTP authentication.
- Condense webhook fields in the notification channel form to display only essential information, mirroring the approach in webhook service.
…int field

- This field will be used to specify the API endpoint for Signal notifications.
- This change aligns the frontend with the backend's data structure for webhooks.
…templating and SSL monitoring

- Add robust notification system supporting 7+ communication channels with intelligent message templating, resource monitoring, and SSL certificate alerts. Notification Channels: (Telegram, Discord, Slack, Signal, Email, Google Chat, Webhooks).

- This notification system provides enterprise-grade alerting capabilities with extensive customization options and multi-channel redundancy for critical service monitoring.
@tolaleng tolaleng merged commit 6462e5c into main Aug 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants