-
-
Notifications
You must be signed in to change notification settings - Fork 658
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
docs: Health check endpoint #3959
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
f2332ea
to
21254fb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me! 😄 I have a few small suggestions, but nothing really very important. Some clarification would be nice some times, but I'll leave it up to you 🙌🏼
Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
We're running into an overloaded concept with operator. This healthcheck endpoint is used in k8s, mesos, docker swarm, pm2. So any application orchestrator. Maybe that's a better word, including somehing like |
Yeah, that sounds like a good call! |
What
Adds documentation for the health check endpoint.