Skip to content

Conversation

@uhthomas
Copy link

@uhthomas uhthomas commented Jul 24, 2023

Related: #702

@uhthomas uhthomas changed the title fix(vmalert): correctly remove notifiers without a selector fix(vmalert): discover vmalertmanagers Jul 24, 2023
@uhthomas uhthomas marked this pull request as draft July 24, 2023 22:06
@uhthomas uhthomas marked this pull request as ready for review July 24, 2023 22:17
@uhthomas
Copy link
Author

Upon further thinking and reading, I'm not sure it will fix the linked issue. However, it definitely does address some problematic assumptions made by the original filtering code. There are a few scenarios where it will do the complete wrong thing, which isn't ideal.

@uhthomas uhthomas force-pushed the 702 branch 4 times, most recently from 223d55f to 834b122 Compare July 24, 2023 22:26
@Haleygo
Copy link
Contributor

Haleygo commented Jul 26, 2023

Upon further thinking and reading, I'm not sure it will fix the linked issue. However, it definitely does address some problematic assumptions made by the original filtering code. There are a few scenarios where it will do the complete wrong thing, which isn't ideal.

Thanks for the pr!
Can you add some scenarios that could be wrong for the origin code in the test file?

@uhthomas
Copy link
Author

@Haleygo Will do.

@AndrewChubatiuk
Copy link
Contributor

covered notifiers discovery here. Nothing suspicious was found besides order, in which discovered notifiers are sorted (its reverse). Closing this as it doesn't fix any issue

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.

3 participants