-
Notifications
You must be signed in to change notification settings - Fork 2.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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 support for service health checks #827
Comments
As suggested by @deviantony open a new ticket. |
I've created a separate issue for the support of |
This seems like a fundamental feature that's missing from portainer. Will this be added? This issue has been open for 3 years and there's still no way to add custom health checks or adjust intervals. I just started using portainer and based on this issue, how many outstanding issues there are and the fact that this issue has been stale for 3 years, not to mention the large number of unmerged PRs, makes me a little hesitant to actually use this is my environment |
Whilst this issue might have been open for 3 years, you will find that substantially more are closed and that the project is likely the richest in regards to functionality.
Currently we are really focussed on our kubernetes support and getting that feature parity with what we have for swarm. Once we get both at a feature parity then we will throw all devs at enhancements, which includes a redesign of the swarm ux, and bringing more enterprise enhancements such as healthchecks.
|
The docker healthcheck functionality isn't considered a core function of docker? I wouldn't consider that an enhancement at all. Kubernetes support though, I would consider that more of an enchancement than healthchecks. You guys have done an amazing job with this but without feature parity with docker from a docker management tool, this just won't work in anything more than a fairly simple deployment |
We're now considering this issue and will add it into our backlog. Requirements
Required changesService list viewIntroduce a new Healthcheck column in the service datatable If the service do not have a configured healhtcheck, display "-". If the healthcheck is OK, display a Healthy green label and if the Healthcheck is KO display an Unhealthy red label. Service creation viewUpdate the Command & Logging tab and add a new Healthcheck section: This section should be composed of:
Service details view
|
@deviantony To define healthcheck status, we need to compute it from all service's containers' statuses. We can only fetch all swarm containers with agent proxy. Which behaviour do you want for non agent connection ? |
@Xuorg actually ignore my mockup about showing the status of the healthcheck associated to the service, it's irrelevant in Swarm. The entire purpose of the Swarm healthcheck is to let Swarm re-schedule tasks when one becomes unhealthy. I think the best would be to provide a visual indicator to see if a Healthcheck is actually set on a service. I would recommend re-using something similar to the resource pool UI/UX for that one:
This is now irrelevant and can be ignored. |
Hi dev Team, when this can be made available? My User Story:
When the same container is stopped and re-started (via Portainer), the no-healthcheck is not used any more and the container gets status "healthy", which means healtcheck is enabled. I want to use '--no-healtcheck' option as Node-Red container has healtcheck enabled by default and it causes excessive logging (Syslog), e.g: This will kill my SSD drive quicker than slower... |
Bumping this as I experience the exact same problem right now - I looked around all of Portainer but couldnt find any way to disabe the healthchecks of containers, quite the surprise |
I need to overwrite the health check cmd while creating or updating containers. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
There are options with docker service that could be useful to users but are not available.
Could we please have them so the rolling updates could work better for users?
The text was updated successfully, but these errors were encountered: