-
Suggestion
-
Resolution: Unresolved
-
None
-
17
-
4
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Currently it's not possible to customers to see any logs of their webhooks being fired on JIRA. Providing users with a way to see those logs via the UI would help customers a lot when troubleshooting issues with their webhooks and diminish support load on requests for those logs.
Workaround
While not available in the GUI, it is possible to write a line to the log file when a webhook is attempting to send.
- Visit Jira Admin -> System -> Logging and Profiling
- Add logging package com.atlassian.webhooks
Now, 2 lines will be logged to the jira log (atlassian.jira.log) file in the JIRA_HOME/log directory. Example:
2021-04-09 09:50:10,432+1000 Web-Hook-Publisher-1 DEBUG admin 590x289x1 19qeghr 127.0.0.1 /rest/api/2/issue/SCR-5/comment [c.a.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Posting to web hook at 'https://webhook.site/testwebhook, body is: SNIP_JSON_BODY_HERE 2021-04-09 09:50:12,039+1000 httpclient-callbacks:thread-1 DEBUG anonymous [c.a.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] WebHook successfully sent
Therefore, these lines can be checked in log to determine when a webhook attempted to send
To make this logging persist past reboots, check article Logging and profiling
- relates to
-
JRASERVER-41388 WebHooks will not log any errors or throw an exception when there's a connection error
-
- Closed
-
-
- Gathering Interest
[JRASERVER-41463] Webhook logging for JIRA
Definately need this functionality. I currently am working on a webhook to send data to an external system. I cannot see any result in the external system, (I know the extrenal system is configured correctly as I can send to it from postman), but there is nothing in Jira that can tell me if the webhook has sent any data. Logging is essential as a stop check to review integration issues.
Hi Team - We need logs for troubleshooting, webhook logs are important for automation used cases. Would be very helpful if this were covered in 2024 releases.
I strongly support this feature! Please prioritise it to make it real sooner. Thank you in advance!
I support this suggestion and I find it would be highly valuable and time-saving in improving and diagnosing our connections/integrations.
I frequently have the need to view this type of log info, and I find the previously mentioned workarounds inconvenient as they require start/stop to enable/disable the java switches. (We can't leave them enabled full-time because it results in a lot of extra logging & can make other troubleshooting tasks confusing/complicated)
Would be useful to have this available as part of being able to mine logs to see if webhooks are actually relevant anymore (the JQL filter could be such that it is always checked, but the specific scenario being compared for no longer would happen in the current user workflow as the issues involved are over and done with)
I would help me on failure tracing. I currently working on an issue were a webhook sent out in time by JSM but got in the aiming application with a huge delay. So the Jira log files might help me here to see were is the root cause.