Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-4101

As a sysadmin, I want to have a healthcheck resource to Crowd

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.8.2
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

            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

            Anders Kvist added a comment - 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
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3362707 ] New: JAC Suggestion Workflow 3 [ 3626298 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1393595 ] New: JAC Suggestion Workflow [ 3362707 ]
            Issue Type Original: New Feature [ 2 ] New: Suggestion [ 10000 ]

            Well, you can catch success like this
            AP.request({
            url: 'https://someone.atlassian.net/rest/api/2/issue/'+issue_id,
            type: 'PUT',
            contentType: 'application/json',
            data: JSON.stringify(data),
            success: function()

            { console.log('it was successful'); }

            });

            David Pankov added a comment - Well, you can catch success like this AP.request({ url: 'https://someone.atlassian.net/rest/api/2/issue/'+issue_id, type: 'PUT', contentType: 'application/json', data: JSON.stringify(data), success: function() { console.log('it was successful'); } });
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 755189 ] New: Simplified Crowd Development Workflow v2 [ 1393595 ]
            Marcin Kempa made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 170918 ]
            Diego Berrueta made changes -
            Link New: This issue is duplicated by CWD-2890 [ CWD-2890 ]
            Marcin Kempa made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 170918 ]
            Marcin Kempa made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 170773 ]
            Marcin Kempa made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 170718 ]

              dberrueta Diego Berrueta
              dberrueta Diego Berrueta
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: