Hello. Wonder if I can include “ports” when showing transactions, or at least be able to break down a transaction at the level more than Stream[localhost]: GET.
Example. We have many urls we call from a given service, at localhost:port. Knowing the port would allow us to break down a long call to localhost:badServicePort.
In specific key traces, we can drill all the way down, but this is not exactly how we need to do it.
I am aware we can create traces with urls manually via the .net agent api set transaction uri. I’d rather not do that unless we need to, and I am not sure that setting a transaction url to localhost:port will do any more than the automatic url gets today from just localhost.
Please advise and thanks.