Azure-docs: Clarification on end-to-end tracing

Created on 12 Sep 2019  Â·  5Comments  Â·  Source: MicrosoftDocs/azure-docs

Could you share more code samples on end-to-end tracing with an end-to-end example?

1> Like a client creating 5 messages in a service bus queue
2> A pool of workers fetching each message individually and processing them
3> Code that enables tracing when a client submits a message
4> Code that enables tracing when worker processes a message
5> Example dashboard on what we get in AppInsights
6> Full code that covers everything

It'd be nice to know exactly what metrics are tracked as well. Eg: Who sent a message, how long in a queue, how long to execute the message, who executed the message, and etc.

Much like this: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues

But "getting started with Service Bus with end to end tracing"


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 assigned-to-author product-question service-bus-messaginsvc triaged

Most helpful comment

+1 on this request. The article is good with lots of information but a sample with walkthrough would be great

All 5 comments

Hi @Infinitism Thanks for your feedback. We will review and update as appropriate.

The biggest help would be in clarifying this part of the blog

"all Service Bus calls done by your service are automatically tracked and correlated with other telemetry items."

What are "other telemetry items"? and does "All service bus calls by your service" include things like who submitted a message? who is processing the message? what's the result of the message?

Needs more insights on what is captured.

@Infinitism I have assigned this to content author for further review and update as appropriate.

+1 on this request. The article is good with lots of information but a sample with walkthrough would be great

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jharbieh picture jharbieh  Â·  3Comments

DeepPuddles picture DeepPuddles  Â·  3Comments

varma31 picture varma31  Â·  3Comments

mrdfuse picture mrdfuse  Â·  3Comments

JeffLoo-ong picture JeffLoo-ong  Â·  3Comments