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 request: TCP health check. #976

Closed
c4milo opened this issue May 26, 2015 · 8 comments
Closed

Feature request: TCP health check. #976

c4milo opened this issue May 26, 2015 · 8 comments
Labels
type/enhancement Proposed improvement or new feature

Comments

@c4milo
Copy link
Contributor

c4milo commented May 26, 2015

No description provided.

@gautamk
Copy link

gautamk commented May 27, 2015

👍

@ryanuber
Copy link
Member

Seems like a useful generic check type, thanks! Also, for the time being, you can just use netcat to get this type of functionality.

nc -z -w5 <host> <port>

@ryanuber ryanuber added the type/enhancement Proposed improvement or new feature label May 28, 2015
@c4milo
Copy link
Contributor Author

c4milo commented May 28, 2015

@ryanuber nice trick! Although, I was thinking more in being able to monitor RDS instances from Consul.

@highlyunavailable
Copy link
Contributor

@c4milo I use TCPing to do just that:

/bin/tcping -t 1 rds.hostname.goes.here 1433

@ryanuber
Copy link
Member

What @highlyunavailable suggest should work too! Both commands would take a hostname and port, which should allow you to do exactly what you need.

@c4milo
Copy link
Contributor Author

c4milo commented May 28, 2015

Cool! Thanks guys!

@Kosta-Github
Copy link

I still think, that a native TCP health check would be helpfull, especially in stripped down docker containers that might not contain nc or tcping ...

@DanyC97
Copy link

DanyC97 commented Jul 16, 2015

i agree with @Kosta-Github

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Proposed improvement or new feature
Projects
None yet
Development

No branches or pull requests

7 participants