Giter Club home page Giter Club logo

Comments (9)

github-actions avatar github-actions commented on August 24, 2024

Thank you for your feedback. Tagging and routing to the team member best able to assist.

from azure-sdk-for-net.

JoshLove-msft avatar JoshLove-msft commented on August 24, 2024

I don't think you'd be able to trace back to the activity that you are creating in your message handler, because the error handler is executed outside the scope of your message handler. However, the entire call of message/error handler is already within a diagnostic scope with activity name "ServiceBusProcessor.ProcessMessage" as mentioned here. Thus any new activities started in your message or error handler will be nested under the SDK span ServiceBusProcessor.ProcessMessage.

from azure-sdk-for-net.

JoshLove-msft avatar JoshLove-msft commented on August 24, 2024

/cc @lmolkova

from azure-sdk-for-net.

github-actions avatar github-actions commented on August 24, 2024

Hi @cjablonski76. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

from azure-sdk-for-net.

cjablonski76 avatar cjablonski76 commented on August 24, 2024

@JoshLove-msft, so how can I trace my message from the publisher all the way down to when an error is thrown?

from azure-sdk-for-net.

JoshLove-msft avatar JoshLove-msft commented on August 24, 2024

@JoshLove-msft, so how can I trace my message from the publisher all the way down to when an error is thrown?

The ProcessMessage span will be linked to the publishing span via the DiagnosticId. Essentially what you are doing in your message handler is already done by the SDK.

from azure-sdk-for-net.

cjablonski76 avatar cjablonski76 commented on August 24, 2024

@JoshLove-msft, so how can I trace my message from the publisher all the way down to when an error is thrown?

The ProcessMessage span will be linked to the publishing span via the DiagnosticId. Essentially what you are doing in your message handler is already done by the SDK.

Ok, I need to get my monitoring setup locally and see what things look like. Will all of my published messages end up having a child span that points to my long running processor spans, do you happen to know?

from azure-sdk-for-net.

JoshLove-msft avatar JoshLove-msft commented on August 24, 2024

The process and send spans should both be children of the Message span, if I'm not mistaken.

from azure-sdk-for-net.

github-actions avatar github-actions commented on August 24, 2024

Hi @cjablonski76, since you haven’t asked that we /unresolve the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve to reopen the issue.

from azure-sdk-for-net.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.