SQL and CosmosDB don't resolve the resource name in trace view

[davidfowl]

It's because the host and port are separated by a comma not a colon (not sure why...). We might need to implement a custom peer resolver for SQL. The address is 127.0.0.1 not localhost and the separator is : not ,.

[davidfowl]

cc @JamesNK

[davidfowl]

Hmm cosmos isn't resolving either. I wonder if we broke peer service resolution when we changed the address from 127.0.0.1 to localhost...

[davidfowl]

Maybe it's just these 2 dependencies. Mongo seems to work.

[JamesNK]

SQL Server uses a comma for port 🤷 Simple fix is to retry on failure with a comma instead of a colon.

Is cosmos a resource? An outgoing peer is only resolved if it is a resource and has an endpoint that matches the client span address.

[davidfowl]

Yea they are both resources. Trying with a comma doesn’t work as the address is 127.0.0.1 vs localhost. Just needs some massaging I guess