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

Slack Plugin Error Handling #635

Open
1 of 13 tasks
waab76 opened this issue Nov 4, 2020 · 1 comment
Open
1 of 13 tasks

Slack Plugin Error Handling #635

waab76 opened this issue Nov 4, 2020 · 1 comment

Comments

@waab76
Copy link
Contributor

waab76 commented Nov 4, 2020

As a Graylog engineer, I want to improve error handling in the Slack Notification plugin in order to better detect, report, and recover from errors.

Input Criteria

  • Slack notifications plugin works

Output Criteria

  • SlackClient no longer uses EventNotificationExceptions
  • SlackClient appropriately signals temporary/recoverable exceptions such as HTTP 5xx codes and network timeout errors
  • SlackClient appropriately signals permanent/unrecoverable exceptions such as HTTP 4xx codes
  • SlackEventNotification properly handles both temporary and permanent exceptions thrown by SlackClient by throwing temporary and permanent EventNotificationExceptions
  • SlackEventNotification raises a UI notification when an permanent exception is encountered
  • JUnit tests exist to validate behavior of SlackClient
  • JUnit tests exist to validate behavior of SlackEventNotification

Tasks

  • Update error handling in SlackClient
  • Update JUnit tests for SlackClient
  • Update error handling in SlackEventNotification
  • Update JUnit tests for SlackEventNotification
  • Manually verify behavior
@waab76 waab76 added this to the 4.0.0 milestone Nov 4, 2020
@waab76 waab76 added the #M > 1d <= 3d label Nov 4, 2020
@waab76
Copy link
Contributor Author

waab76 commented Nov 19, 2020

Slack returns 429 for too many requests, need to consider how to handle that

@bernd bernd removed this from the 4.0.0 milestone Jan 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants