Add otp-watch to Observability & Monitoring - #528
Open
flovoice53-tech wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
otp-watch is a small hosted service that answers a question standard synthetic monitoring doesn't: did the OTP/verification SMS or email a signup flow sent actually arrive, and how fast? You get a real phone number or disposable email, trigger your own send to it, then poll for arrival/latency. Fits right next to Healthchecks (cron delivery monitoring) as a delivery-confirmation tool rather than an infra-metrics one.
Repo: https://github.com/flovoice53-tech/otp-watch
Live: https://otpwatch.flo-voice1.com