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

Add status page w/reliability+uptime ping tests #22

Closed
niftylettuce opened this issue Jul 28, 2018 · 14 comments
Closed

Add status page w/reliability+uptime ping tests #22

niftylettuce opened this issue Jul 28, 2018 · 14 comments

Comments

@niftylettuce
Copy link
Collaborator

No description provided.

@MattIPv4
Copy link

MattIPv4 commented Feb 26, 2019

@niftylettuce Hey, would you like help with this?
I'm sure I can talk to some people at Statuspage/Pingdom and see if they'd be happy to hook you up :)

@niftylettuce
Copy link
Collaborator Author

That'd be fantastic!

@MattIPv4
Copy link

@niftylettuce Could I possibly be added as a collaborator so that I appear as "part of" the project for Statuspage so they know I am contacting them properly ob behalf of the project? :D

@MattIPv4
Copy link

Also, do you have a list of what service components you’d like on the status page?

And what domains/URLs I should ping in Pingdom for uptime and response time metrics?

@niftylettuce
Copy link
Collaborator Author

mx1.forwardemail.net
mx2.forwardemail.net
forwardemail.net

@niftylettuce
Copy link
Collaborator Author

Sorry for the delay - just did a major improvement and overhaul, see #101 (comment) for a detailed explanation.

@MattIPv4
Copy link

MattIPv4 commented Mar 12, 2019

@niftylettuce Could I be added to the repo as a collab?
And will it just be a ping on those three domains to check uptime?

Edit: Would a HTTP Get check for forwardemail.net be better?
I assume it will need to be a ping for the MX servers?

@niftylettuce
Copy link
Collaborator Author

niftylettuce commented Mar 12, 2019

@MattIPv4 answers below:

  1. HTTP GET with response code of 200 for forwardemail.net should be OK
  2. telnet mx1.forwardemail.net 25 followed by helo (optionally ehlo) and then quit maybe to ensure SMTP connection working
  3. repeat (2) above but for mx2.forwardemail.net

I don't have an org setup yet for this repository/project 😦

P.S. I tried to get a hold of @indus from JS.ORG, since he is using ImprovMX instead of ForwardEmail.net - maybe you can ping him to switch to something private and secure, AND OPEN SOURCE! 😄 ?

@MattIPv4
Copy link

@niftylettuce Awesome.

You should be able to add me directly as a collaborator to this repo, which should hopefully be enough to convince any company looking in that I'm here to help as part of the project :)

With regards to js.org - I suggested improv over this simply because it keeps the target email addresses private, whereas with this they're public in txt records. I personally use a mixture or improv and forwardemail throughout my own projects.

@X1Aaron
Copy link
Contributor

X1Aaron commented Sep 5, 2019

@niftylettuce
Copy link
Collaborator Author

@aaronstuder thanks 👍 that's nice to have for now! I have a status page that I'll launch on v2.0.0 but that is really really helpful for a temporary solution until then. Looks nice

@MattIPv4
Copy link

MattIPv4 commented Sep 5, 2019

Is there still a plan to move this to its own org at some point?

@niftylettuce
Copy link
Collaborator Author

Yes @ParveenBhadooOfficial but they do not satisfy my requirements.

Closing for organization purposes in favor of #189 where this will be added very shortly as a release checklist item. Please follow/subscribe to that issue for further updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@X1Aaron @niftylettuce @MattIPv4 and others