Monitoring message queue performance with Sentry #69320
Replies: 2 comments 1 reply
-
Exciting! Been tracing manually with |
Beta Was this translation helpful? Give feedback.
-
Trying to understand the distinction between this and your mockups. Does this mean we can see published vs processed in any time period, but not total count in the queue at any one time? Is there a meaningful distinction between total and published - processed? Trying to think if that would matter to us, I don't think it does! Re: infrastructure/libraries. We use Azure Service Bus. Library wise we use .NET and We use both Queues and Topics and subscriptions, but the latter a lot more https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions Would you say your area of focus is more about Queues, or is your definition of a Queue loose enough to encapsulate both? |
Beta Was this translation helpful? Give feedback.
-
Messaging systems, such as Celery, or SQS, are a useful abstraction. However, they can be challenging to reason about:
We’re working on a feature at Sentry that makes your application’s interactions with message queues easier to reason about…
Queue performance insights
These are some of the metrics we felt would be valuable for identifying queue performance problems:
Request for feedback
If you build applications that use messaging systems, we’d love your feedback on this feature.
To get the ball rolling 🏀 …
Mockups
Queue overview page
This is the first page that you’ll see when you click on Queue insights. In this view, you will see a high level summary of queue performance across all the queues and topics used by your system (depending on what queue you’re using, this may be a topic, or queue name).
Destination summary
This page provides similar metrics to the Queue overview page, but broken down by Destination. The Queue overview page helps you see the behaviour of your queues at 30’000’, the Destination Summary page allows you to better understand specific queue performance issues.
Transaction Overlay
Producer overlay
Consumer overlay
The Transaction Overlay, along with showing transaction level metrics, displays a sample of spans representing messages that were recently either written to the queue, or processed from the queue.
For both consumers and producers, you can dig deeper by clicking the Span ID and viewing the trace tied to the queue operation.
Looking forward to people’s feedback in this discussion,
— @bcoe
Beta Was this translation helpful? Give feedback.
All reactions