Http DependencyTelemetry data structure is inconsistent with .NET SDKs

[lmolkova]

Java SDK reports method and URI in custom dimensions (in .NET SDKs it's dependency name and target)
while reporting instrumented method in the name and target

There are other potential discrepancies (e.g. for successful outgoing http request request target reported in 'cid-v1:' )

Java SDK should follow telemetry data structure and be consistent with .NET SDKs.

[dhaval24]

@lmolkova thank you very much for reporting the inconsistency in HTTP DependencyTelemetry datastructure. If I recall correctly both Dot Net and Java SDK share the same Bond definition which is use
e the same Bond definition which is used to generate the DependencyData data-structure so ideally this difference should not arise, I would have to double check, however let me ask you this question :

1. As you mentioned that custom dimension in Dot Net is reported as dependency name and target so it should be like this {Dependency Name = GET, target = URL } what does target look like ? Isn't it URI ?
2. What does Dot Net SDK show in case of successful dependency call in target field. I have no idea from where the cid-v1 is getting populated in Java.

[lmolkova]

@dhaval24

As per Dependency Collector code in .NET (e.g. here and here)

Name = method + aboslute path
Target = host

Example

[lmolkova]

Update: there might be different behavior for 'target' in case of same i-key and multiple i-keys, but I'm not aware of the details

[dhaval24]

@lmolkova #567 should fix this.