Queue Mappings

In case you are using Atomic Scope for monitoring your business transactions that are running through Azure Logic Apps, Service Bus Queues are used as intermediate storage between Azure and Atomic Scope.
This article answers some frequently heard questions about how this synchronisation mechanism works.

Is there a limit on how many queues that can be mapped ?

Yes, you can map a maximum of 10 queues to Atomic Scope

What happens to my activites when I upgrade from v7.x or older ?

• The activities which are received in portal will not be affected
• The activities which are yet to be processed or any pending events from the EventHub will not be available. It's the responsibility of the Atomic Scope administrator to alert for maintenance and prevent all Logic Apps or processing services that are throwing activities before performing a upgrade to v7.5

I have a transaction that spans across Logic Apps. Do I need to pass the same Id in all instances ?

We generally recommend you to do so. But even if the Id is not received, the activity will be sent to the default queue and will be processed by Atomic Scope, ensuring that no events are gone missing.

Known Limitations

No matter even if you add more queues, if you hit the Azure Service Bus Quota Limit it is out of Atomic Scope to fix this or take this into consideration. We recommend to split your load across queues, so even on a very to extremly high load, you don't hit the 5000 concurrent connection limit.