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

Asymmetric Recovery #1176

Closed
sapiderman opened this issue Nov 13, 2023 · 0 comments · Fixed by #1210
Closed

Asymmetric Recovery #1176

sapiderman opened this issue Nov 13, 2023 · 0 comments · Fixed by #1210
Assignees
Labels
bug Something isn't working

Comments

@sapiderman
Copy link
Contributor

sapiderman commented Nov 13, 2023

Describe the bug

  1. When identical probes encounter incident, notifications sent to all of them.
  2. But when Recovered, only one notification is sent.

To Reproduce
Steps to reproduce the behavior:

  1. use the following config:
probes:
  - id: 'mock-1'
    name: 'local-test'
    requests:
      - url: http://0.0.0.0:7001/v1/hello
    alerts:
      - assertion: response.status != 200
        message: message 11

  - id: 'mock-2'
    name: 'local-test-no-alert'
    requests:
      - url: http://0.0.0.0:7001/v1/hello

  - id: 'mock-3'
    name: 'local-test-no-alert'
    requests:
      - url: http://0.0.0.0:7001/v1/hello
  1. Disable the local server (0.0.0.0)
  2. Expect 3 incident notifications sent
  3. Turn back on the local server (0.0.0.0)
  4. Expect 3 recovery notifications sent... but only one received

Screenshots

  1. Startup and Incident
    image

  2. Recovery:
    image

  3. Email, startup, incident, recovery notifications.
    image

Desktop (please complete the following information):

  • OS: Linux Ubuntu 22.04
  • From src: main brnach
@sapiderman sapiderman added the bug Something isn't working label Nov 13, 2023
@sapiderman sapiderman self-assigned this Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant