Skip to content

Commit b16afa4

Browse files
authored
Merge pull request #110669 from spelluru/sbusstorage0408
added a note
2 parents 1315397 + ff9ba27 commit b16afa4

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/service-bus-messaging/message-counters.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.workload: na
1212
ms.tgt_pltfrm: na
1313
ms.devlang: na
1414
ms.topic: article
15-
ms.date: 01/24/2020
15+
ms.date: 04/08/2020
1616
ms.author: aschhab
1717

1818
---
@@ -41,6 +41,11 @@ Knowing the active message count is useful in determining whether a queue builds
4141

4242
If an application wants to scale resources based on the length of the queue, it should do so with a measured pace. The acquisition of the message counters is an expensive operation inside the message broker, and executing it frequently directly and adversely impacts the entity performance.
4343

44+
> [!NOTE]
45+
> The messages that are sent to a Service Bus topic are forwarded to subscriptions for that topic. So, the active message count on the topic itself is 0, as those messages have been successfully forwarded to the subscription. Get the message count at the subscription and verify that it's greater than 0. Even though you see messages at the subscription, they are actually stored in a storage owned by the topic.
46+
47+
If you look at the subscriptions, then they would have non-zero message count (which add up to 323MB of space for this entire entity).
48+
4449
## Next steps
4550

4651
To learn more about Service Bus messaging, see the following topics:

0 commit comments

Comments
 (0)