Skip to content

Support sending non-state notifications without an incident#188

Closed
yhabteab wants to merge 8 commits intonon-state-notification-types-v1from
yhabteab/support-non-state-notification-types
Closed

Support sending non-state notifications without an incident#188
yhabteab wants to merge 8 commits intonon-state-notification-types-v1from
yhabteab/support-non-state-notification-types

Conversation

@yhabteab
Copy link
Copy Markdown
Member

@yhabteab yhabteab commented Apr 25, 2024

Facilitates sending non-state notifications even without an active incident. See the individual commits separately for the details of why something was changed and most of them also contain their own reasons.

Blocked by

resolves #106

@cla-bot cla-bot bot added the cla/signed CLA is signed by all contributors of a PR label Apr 25, 2024
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch from 0431265 to 62d1ceb Compare April 25, 2024 15:24
@yhabteab yhabteab requested a review from julianbrost April 25, 2024 15:24
@yhabteab yhabteab force-pushed the send-incident-non-state-notifications branch 2 times, most recently from 796ff00 to 0ff79aa Compare April 26, 2024 10:19
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch 5 times, most recently from c2743ba to 8ba8889 Compare April 26, 2024 15:30
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch 3 times, most recently from b7dd933 to 68811f7 Compare May 8, 2024 14:44
@yhabteab yhabteab requested review from julianbrost and oxzi and removed request for julianbrost May 8, 2024 14:45
@yhabteab
Copy link
Copy Markdown
Member Author

yhabteab commented May 8, 2024

Please review concept and functionality, but be aware that there is no corresponding web PR yet.

@yhabteab yhabteab force-pushed the send-incident-non-state-notifications branch from 8c380a1 to e2269d2 Compare May 13, 2024 12:27
Base automatically changed from send-incident-non-state-notifications to main May 13, 2024 15:45
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch from 68811f7 to 11b142c Compare May 15, 2024 09:20
Comment thread internal/rule/rule.go Outdated
Comment thread internal/rule/rule.go Outdated
Comment thread internal/events/router.go Outdated
Comment on lines +66 to +77
if i != nil {
if err := i.ProcessEvent(ctx, ev); err != nil {
if errors.Is(err, event.ErrSuperfluousStateChange) {
return err
}

// Expect the actual error to be logged with additional context in the incident package.
return event.ErrEventProcessing
}

return nil
}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So if an Incident exists, the other rules aren't even considered? That shouldn't be the case, if you configure that you want to be notified about downtimes, you should be notified about all of them.

@yhabteab yhabteab removed the request for review from oxzi May 17, 2024 07:46
@yhabteab yhabteab marked this pull request as draft May 17, 2024 07:46
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch 3 times, most recently from 563d4f0 to a9c9105 Compare August 1, 2024 11:49
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch 2 times, most recently from 3115913 to b6e0bad Compare September 8, 2025 15:17
@yhabteab yhabteab force-pushed the non-state-notification-types-v1 branch from 8dc0902 to 07d937b Compare September 10, 2025 11:47
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch 3 times, most recently from 09ba57c to 3560459 Compare September 10, 2025 14:14
@yhabteab yhabteab force-pushed the non-state-notification-types-v1 branch from a887713 to cf1fcb3 Compare October 27, 2025 15:37
@julianbrost julianbrost added this to the 0.2.0 milestone Oct 28, 2025
@yhabteab yhabteab force-pushed the non-state-notification-types-v1 branch from cf1fcb3 to 6e43246 Compare October 30, 2025 10:45
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch 5 times, most recently from 5b0bcd8 to 95183f1 Compare October 30, 2025 12:48
@yhabteab yhabteab force-pushed the non-state-notification-types-v1 branch from 05231b6 to 4d3bf72 Compare November 3, 2025 15:55
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch from 95183f1 to 932c1f4 Compare November 3, 2025 15:56
@yhabteab yhabteab force-pushed the yhabteab/support-non-state-notification-types branch from 932c1f4 to a7833f1 Compare November 3, 2025 16:13
@yhabteab yhabteab removed their assignment Nov 4, 2025
@yhabteab yhabteab removed this from the 0.2.0 milestone Nov 4, 2025
@yhabteab
Copy link
Copy Markdown
Member Author

yhabteab commented Nov 4, 2025

NOPE!

@yhabteab yhabteab closed this Nov 4, 2025
@yhabteab yhabteab deleted the yhabteab/support-non-state-notification-types branch November 4, 2025 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla/signed CLA is signed by all contributors of a PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Additional notifications: notifications without an incident + incident meta notifications

2 participants