Skip to content
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

Sequence Manager: report sequencing failures to #biobots channel #875

Open
reisingerf opened this issue Feb 21, 2025 · 1 comment
Open
Assignees
Labels
feature New feature

Comments

@reisingerf
Copy link
Member

Sequencing failures are generally not recoverable, so any failures or errors should be flagged asap for end users (i.e. the #biobots Slack channel). This should be based on the Sequence Managers internal state handling, e.g. focus on sequencing events and not BSSH analysis events (i.e. events before PendingAnalysis)

@raylrui
Copy link
Contributor

raylrui commented Mar 5, 2025

PR #886 merged.

When deployed to prod, I will add this resource policy to the SNS topic to allow orcabus to send events to this topic.

{
      "Sid": "AWSEvents_OrcaBusProd-SequenceRunManagerStackSlackNotificationRule_Id85755e27-3dd5-408e-9091-9cbc7315db7e", // uuid will be new generated
      "Effect": "Allow",
      "Principal": {
        "Service": "events.amazonaws.com"
      },
      "Action": "sns:Publish",
      "Resource": "arn:aws:sns:ap-southeast-2:843407916570:AwsChatBotTopic-alerts"
 }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

2 participants