-
Notifications
You must be signed in to change notification settings - Fork 67
Dependency calls to cosmosdb (graph) implementation #969
Comments
do you specify TCP connection policy? ApplicaitonInsights supports HTTP connections only. If you use HTTP, you probably experience #919 or #739 Please try Dependency Collector v 2.7.0-beta4, we are working on releasing the stable version in a couple of weeks. |
Adding few more details: We make calls to Azure blob as well as cosmosdb (graph) and other HTTP endpoints.
We are using AI on owin self-hosted application and the dependency calls are not working above 2.3.0 version ( we have a separate issue for this https://github.com/Microsoft/ApplicationInsights-dotnet-server/issues/968) |
Have you tried 2.7.0 version? Does it reproduce on 2.7.0 as well? |
With 2.7.0 looks like the other issues is resolved i.e. dependency calls are getting tacked for us (i.e. it was working only until version 2.3.0 for our owin self host app earlier), however, still only the first call to cosmosdb(graph) is captured as a dependency, other dependencies are getting captured as expected. |
It seems Gremlin uses |
Thanks for the update, @lmolkova , infact we are using "HTTP request in Owin self-hosted app" mentioned in the article you referred above, will look into this piece as well "Outgoing dependencies tracking" and use it as appropriate. Thanks again! |
@reachravig I can try to dig into the first call tracing if you could provide a small app that reproduces the problem (please strip all credentials). |
Sure, will send you our code sample and details via email. |
We have a cosmosdb (graph) implementation via web socket where the application is maintaining singleton.
We fired multiple requests to the endpoint, only the first request shows the dependency call to the cosmosdb (graph) and the subsequent doesn’t, is this expected?
The text was updated successfully, but these errors were encountered: