feat: add pagerduty, opsgenie, and matrix notifications#4598
Open
Shubhangam-Singh wants to merge 1 commit into
Open
feat: add pagerduty, opsgenie, and matrix notifications#4598Shubhangam-Singh wants to merge 1 commit into
Shubhangam-Singh wants to merge 1 commit into
Conversation
dosubot
Bot
added
size:XXL
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces three new enterprise-grade notification providers: PagerDuty, Opsgenie, and Matrix.
Many production deployments require structured incident management rather than simple chat pings. This addition allows Dokploy users to seamlessly hook up critical alerting events directly to on-call schedules and decentralized messaging solutions.
Key Changes:
Database layer: Extended the Drizzle schema to support pagerduty, opsgenie, and matrix relationships linked to the main notifications table, including generating the corresponding SQL migration.
Backend logic: Added full CRUD operations via the tRPC router and service layers.
Dispatch integrations: Updated all 8 core application dispatchers (build errors, database backups, server thresholds, docker cleanups, etc.) to evaluate and trigger the new provider pipelines.
Frontend UI: Integrated the 3 new providers smoothly into the configuration wizard (handle-notifications.tsx) leveraging type-safe discriminated zod unions and active mutation mappings.