-
Suggestion
-
Resolution: Fixed
-
None
-
None
This change adds a health check resource at:
http://localhost:8095/crowd/rest/healthcheck/1.0/check
that will return a successful 200 (OK) or 204 (No content) to indicate that Crowd is running.
Any registered internal healthchecks may cause this to fail, and details of the problems will be included in the response.
[CWD-4101] As a sysadmin, I want to have a healthcheck resource to Crowd
Workflow | Original: JAC Suggestion Workflow [ 3362707 ] | New: JAC Suggestion Workflow 3 [ 3626298 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393595 ] | New: JAC Suggestion Workflow [ 3362707 ] |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 755189 ] | New: Simplified Crowd Development Workflow v2 [ 1393595 ] |
Remote Link | Original: This issue links to "Page (Extranet)" [ 170918 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 170918 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 170773 ] |
Remote Link | Original: This issue links to "Page (Extranet)" [ 170718 ] |
How come this is marked as fixed, when a default Crowd install still doesn't respond to /status like Jira and Confluence does?
I hope I'm wrong, but a default install (without any configuration) of 4.1.2 from https://hub.docker.com/r/atlassian/crowd has the status on /crowd/status where both Jira and Confluence has it on /status