Open
Conversation
Runs from cron and fires once per unique event to avoid spam: - pgcopydb process stopped unexpectedly - New ERROR lines in migration.log - Migration completed (success or failure) Alert messages include tables copied and GB transferred, sourced from the pgcopydb SQLite catalog. State is stored in $MIGRATION_DIR/.notify-state and resets automatically when a new migration starts. README: added usage to the Monitor section and script reference table.
…EBHOOK_URL to .env; decouple monitoring from start-migration-screen.sh
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.
Slack monitoring :
slack-migration-alerts.sh - slack alerts for pgcopydb migration events
ALERTS FIRED when: