Azure ServiceBus Receive Transaction not accessible as `CurrentTransaction`
See original GitHub issueAPM Agent version
1.10.0
Environment
Operating system and version: Linux
.NET Framework/Core name and version: .NET 5
Application Target Framework: ASP.NET Core Runtime 5.0.6
Describe the bug
With the new Azure ServiceBus support, apm-agent correctly creates transactions for every received message.
However, the transaction does not contain any spans and creating spans manually fails because there is no CurrentTransaction
.
Expected behavior
Calling Tracer.CurrentTransaction()
in a message handler returns the automatically created transaction.
Actual behavior
Calling Tracer.CurrentTransaction()
in a message handler returns null.
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Overview of transaction processing in Azure Service Bus
This article gives you an overview of transaction processing and the send via feature in Azure Service Bus.
Read more >Azure ServiceBus JMS transaction support not clear
Im working on standard Java/Spring Boot stack interfacing with Azure Service Bus. No Qpid JMS. The JMS over AMQP approach is implemented in ......
Read more >Public API | APM .NET Agent Reference [1.x]
Returns the currently active transaction. See the Transaction API to customize the current transaction. If there is no current transaction, this method will ......
Read more >Azure Service Bus .NET SDK Deep Dive – Atomic Sends
If we execute the sends within the transaction scope we can see message are not available until the transaction scope is completed. Once...
Read more >Capture from SQL Server using Direct Transaction Log ...
The Direct Transaction Log Access method and pipelined execution ensures optimum efficiency to keep up with the database log writers.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@oleschoenburg I’ve opened #1331 to address
Great explanation @russcam! I agree that a transaction spanning the entire chain from
Receive.Start
toProcessMessage.Stop
would be ideal. Just having a transaction fromProcessMessage.Start
toProcessMessage.Stop
seems like a decent compromise though and would be good enough for my use case.