Issue Summary

• Usage of Webhook name in the logger would be unique and usable. Endpoint is not necessarily unique.
• If the webhook doesn't return a 200 success code, log it as a WARN by default without having to turn on additional logging.
• Also, log WARN or ERROR logging with the webhook name whenever it is rejected or dropped from the internal queuing before being invoked.
• If a webhook doesn't work for some reason, make it easy to identify and alert in standard tooling within Jira

Expected Results

Share the webhook name in the logger so that it will be more convenient to identify which webhook has the issue.

Actual Results

Currently when trace logging is enabled for com.atlassian.webhooks, it shows the id which is the primary key on the AO_A0B856_WEBHOOK table.

webhook-dispatcher:thread-1 TRACE anonymous [c.a.webhooks.internal.DefaultWebhookService] A new webhook invocation has been created for webhook [1], invocation [da8631d1-aea2-4075-a173-ae958ffc23ed] 

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available