-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
6
-
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.
- is related to
-
JRASERVER-41388 WebHooks will not log any errors or throw an exception when there's a connection error
-
- Closed
-
-
- Gathering Interest
- relates to
-
- Closed
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[JRASERVER-39361] We should improve the Webhooks logging
Not just having the failed web hooks, but a log of all web hooks actually invoked would help in the case of wanting to clean up potential obsolete web hooks (say based on JQL for projects or issues no longer active). I would be having these logs going to splunk or similar so could do a historical analysis.
I'd like to see these logs made available in the admin UI and available to those who don't run their own Jira server (i.e. no access to `atlassian-jira.log`).
An example of this kind of functionality can be compared to GitHub's log of webhooks.
Could we also have Webhook logs has appended to another log file other than atlassian-jira.log
I agree that the logging and activity details for webhooks in Jira Server need to be updated. David's comment about how Bitbucket logs and details the activity is exactly what we need or some way through the API to get the details.
An example of a detailed webhook log can be seen in Bitbucket Server https://confluence.atlassian.com/bitbucket/troubleshoot-webhooks-757727842.html
Hi,
JIRA web hook log is very important to us. But for now it cannot include the necessary information in the log.
Background:
Previously we regularly call JIRA API to get JIRA incremental data. But it's not real time data. Considering JIRA web hook could provide real time data, we use web hook to do the JIRA data ingestion. But the problem is JIRA web hook information are not stored in log file when have any issues that result in data missing.
Requirement:
We expect every JIRA web hook information can be stored in the log. Especially put the JIRA web hook json data in the log when it's not successfully sent out (Say, connection issue with the consumer service). We can recover the web hook data based on the log in case missing some data.
we can also do the JIRA web hook monitoring based on the log. Else we are not sure if the web hook are send out correctly or not.
Thanks,
Ares
There are improvements in latest available releases. These improvements are captured in
JRASERVER-41388.