-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation on dependency logging not up to date #449
Comments
Hi Arnaud, thx for the issue. I can see your confusion. This, however, is not a mistake or bug but was done on purpose. Tracking dependencies happens in two parts:
In order for Arcus to know how the called dependency is calling itself, a dependency ID has to be passed while logging the dependency. We are working on a set of extensions that extends the Service-to-service correlation is a very complex topic to get right, so we are working also on several user guides to help consumers in this process. 👍 |
We could, however, add the |
@stijnmoreels thank you for the explanation, I would like to pick this up and update the docs 😃 |
Great! Thx for the help! |
@meersschautarnaud , letting you know that with the new Arcus telemetry in Web API/Messaging, we can now automatically track Microsoft dependencies (HTTP, SQL, all Azure dependencies...) without any additional Arcus dependency tracking. |
Describe the bug
Looking at the documentation on how to log a service bus dependency it shows a method that is obsolete. Next to that in the new methods, you need to provide a dependencyId which is a bit confusing since correlation is normally handled by Arcus itself, but this is probably another discussion.
Additional context
The text was updated successfully, but these errors were encountered: