Skip to content

feat(SQO): Introduce Slack notification pipeline and test script for failed/successful runs of the SQO #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Jun 9, 2025

Conversation

MoonBoi9001
Copy link
Member

@MoonBoi9001 MoonBoi9001 commented Jun 6, 2025

Motivation

When the SQO runs on its scheduled timelines we would like an initial internal notification system that integrates with Slack. This helps with monitoring while the SQO is in the early phases of development.

Details

Slack Integration with Scheduled Runs

  • Success Notifications: Sent after each successful oracle run with transaction details and processing metrics
  • Failure Notifications: Sent when errors occur during scheduled execution with detailed error information
  • Direct Integration: Notifications are sent directly from the oracle process (service_quality_oracle.py) during scheduled runs

Reliability Features

  • Exponential backoff retry (1s → 2s → 4s) for network resilience
  • Non-blocking: Oracle continues running even if notifications fail

Testing

export SLACK_WEBHOOK_URL="webhook_url"
./scripts/test_slack_notifications.py

@MoonBoi9001 MoonBoi9001 marked this pull request as ready for review June 9, 2025 12:18
@MoonBoi9001 MoonBoi9001 merged commit d50ab59 into main Jun 9, 2025
9 checks passed
@MoonBoi9001 MoonBoi9001 deleted the TODO_continue_2 branch June 9, 2025 12:19
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.

1 participant