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.

Sign up for GitHub

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

Jump to bottom

Does the retry logic apply to DNS lookups in addition to Teams notification attempts? #74

Open
atc0005 opened this issue May 18, 2020 · 0 comments
Open

Does the retry logic apply to DNS lookups in addition to Teams notification attempts? #74

atc0005 opened this issue May 18, 2020 · 0 comments
Assignees
@atc0005
Labels
question Further information is requested
Milestone
Future

Comments

@atc0005
Copy link
Owner

atc0005 commented May 18, 2020

Found this in a Nagios email alert today:

Additional details: dial tcp: lookup outlook.office365.com on 192.168.82.12:53: read udp 192.168.3.91:34394-192.168.82.12:53: i/o timeout

The corresponding Teams notification didn't make it through, presumably for the same DNS lookup failure that caused the remote mailbox service check to fail. I need to review the code to make sure that DNS related errors are covered by the same intended retry behavior that applies to webhook URL submissions.
@atc0005 atc0005 added the question Further information is requested label May 18, 2020
@atc0005 atc0005 added this to the Future milestone May 18, 2020
@atc0005 atc0005 self-assigned this May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@atc0005 atc0005

Labels
question Further information is requested
Projects
None yet
Milestone
Future
Development

No branches or pull requests
1 participant
@atc0005