JIRA Soap Service log and Access filter log footprint needs improving - Invoked Method would be handy

Currently when a SOAP request comes into JIRA it lands on the AXIS servlet.

/jira/rpc/soap/jirasoapservice-v2

This is because its a POST and not a GET.

What this means is that it hard to tell what "service method" was being invoked.

From a support point of view, you cant tell what "SOAP method" is taking a long time compared to some other SOAP method or how often one method versus another is being invoked.

JIRA needs a better way to display this information.

Perhaps a second log could be added for SOAP requests. Perhaps a setting to cause this to go to the main log could be added.

We would at least need the "method" being invoked, so support can better work out what is going on