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

feature: require N check-ins #1

Open
adamdecaf opened this issue Dec 7, 2022 · 4 comments
Open

feature: require N check-ins #1

adamdecaf opened this issue Dec 7, 2022 · 4 comments
Labels
enhancement New feature or request

Comments

@adamdecaf
Copy link
Owner

Often we may be running N instances of a service and expect them all to checkin. If not all services checkin then we'd want to alert somehow.

Use-case: If there are N kafka consumers staging work (e.g. achgateway) and none of them have work to commit (e.g. upload) then we could notify folks to expect zero commited work. (e.g. if there are zero pending files then expect no file uploaded)

@adamdecaf adamdecaf added the enhancement New feature or request label Dec 7, 2022
@alovak
Copy link

alovak commented Feb 8, 2023

How would you distinguish instances between each other?

@adamdecaf
Copy link
Owner Author

How would you distinguish instances between each other?

Good question. I was thinking we could store some state in PagerDuty and check-in requests could de-dup based on the request headers/contents.

@adamdecaf
Copy link
Owner Author

Similarly we may want to accept a checking with a score of N and fire alerts if N is below some threshold.

@adamdecaf
Copy link
Owner Author

Still not sure how to do this in a provider agnostic way. We've got PD working (finally) and will just split out -0 and -1 into different checks.

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

No branches or pull requests

2 participants