HTTP method for transaction naming in newrelic config file

[leongc-sportsbet]

Is your feature request related to a problem? Please describe.

We have transactions that aren't instrumented in the code and therefore we are using the configuration file to set transaction names based on the path. We do have transactions that may be a POST /abcd or GET /abcd but the current options only utilises the path name and so does not work for where we have HTTP method overloading

Feature Description

The ability to to specify the HTTP method as an optional parameter for the transaction naming rules

Describe Alternatives

A clear and concise description of any alternative solutions or features you've considered. Are there examples you could link us to? N/A

Additional context

An example of what I'd like to see would be:

rules: {
            name: [
                { pattern: "/abcd", method: "GET", name: "GET_abcd" },
                { pattern: "/abcd", method: "POST", name: "POST_abcd" },
                { pattern: "/abcd", method: "PUT", name: "PUT_abcd" }
]}

Priority

Please help us better understand this feature request by choosing a priority from the following options:
[Really Want]

[workato-integration]

https://issues.newrelic.com/browse/NEWRELIC-7811