Incorrect transaction name change reported in logs when SetTransactionName is called multiple times

[nrcventura]

Description

FINEST level logs generated by CandidateTransactionName.TrySet are not accurate if the SetTransactionName API method is called multiple times in a single transaction. Currently the agent logs indicate that the transaction name specified in the second call to the SetTransactionName API is ignored, but the code does not ignore that name and instead keeps it. The log message is incorrect.

Expected Behavior

If the current transaction name, and the new transaction name both have a priority of User, the log message should indicate that the transaction name is changed to the new transaction name. Doing this will make the log message consistent with the actual logic.

Troubleshooting or NR Diag results

Steps to Reproduce

1. Create a transaction
2. Call the SetTransactionName API with a value such as NameFromFirstCall
3. Call the SetTransactionName API with a new value such as NameFromSecondCall
4. Observe that the logs indicate that the transaction name NameFromSecondCall is ignored, even though the transaction data shows that the transaction name is NameFromSecondCall is used for the transaction event and the scoped metrics.

For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5): P4
Suggested T-Shirt size (S, M, L, XL, Unknown): S

[workato-integration]

https://issues.newrelic.com/browse/NR-152680