Closed tirish closed 7 years ago
@KamilSzostak @SergeyKanzhelev
Client-side JS SDK may be incorrect in giving you telemetry formatted this way. Here's a screenshot from the latest .NET SDK which Node.js should be replicating.
Ah, I am also seeing that from our .NET applications as well. I guess it is working as intended, I just wish there were some indication of HTTP method. Do you know if that information is available in some not-obvious way from the portal?
This seems to be an accidental regression to me when we changed how we format our telemetry. I'm not seeing it available in any fields. @SergeyKanzhelev should be able to say what the intended output is here.
Investigated further - this was actually caused by an error in our backend ingestion service. When the fix is deployed out future telemetry should have the following form for a dependency to http://test.com/page
Name: GET /page Target: test.com Data: http://test.com/page
Thanks @OsvaldoRosado !
How our auto-collected HTTP dependencies from our node app are showing up:
Notably missing: The
GET
in the dependency name Less notably missing: The port at the very top of the blade, the path in dependency nameGood example from auto collected client-side AJAX dependency: