Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-39361

We should improve the Webhooks logging

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Webhooks
    • 4
    • 6
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      If a webhook POST fails, in most cases we only get the HTTP error code in the JIRA logs, as the example below:

      2014-07-29 12:07:31,550 webhooks-http-retriever:thread-2 ERROR      [webhooks.util.http.CachingHttpContentRetriever] Unable to post to http://jira.test.com/test due to HTTP/1.1 400 Bad Request
2014-07-29 12:07:44,173 webhooks-http-retriever:thread-3 ERROR      [webhooks.util.http.CachingHttpContentRetriever] Unable to post to http://jira.test.com/test due to HTTP/1.1 400 Bad Request
2014-07-29 12:08:04,362 webhooks-http-retriever:thread-4 ERROR      [webhooks.util.http.CachingHttpContentRetriever] Unable to post to http://jira.test.com/test due to HTTP/1.1 400 Bad Request

      It would be good to allow logging the entire HTTP response as well (e.g. by increasing the logging level), as it may contain information which can help during the troubleshooting process when the webhook is not working.

            Unassigned Unassigned
            dconrad Danilo Conrad
            Votes:
            40 Vote for this issue
            Watchers:
            28 Start watching this issue

              Created:
              Updated: