-
Notifications
You must be signed in to change notification settings - Fork 781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Message filtering & Visibility of session state object in Azure Service Bus Explorer #656
Comments
@rohit3d2003 for 1, would this be a filter you can apply after peeking / receiving messages, or something that should be done as part of the peek / receive. The first one we might be able to do today, the second would require a change on the service side. |
@EldertGrootenboer - I am thinking of a scenario where there are 1000 messages in dead letter queue and the support team is looking to filter messages by Session Id or some other property as part of peek operation to reduce the number of messages they see |
Thank you for suggesting this feature. We have opened an investigation task for this in our backlog, and will update this issue when we have more information. To help us get this prioritized, it would be helpful to see others vote and support this feature, as well as explain their scenarios. |
Thank you for your feedback on this item, it helps us in our efforts to continuously prioritize the different requests we get from all our various feedback channels. We have added this feature in our backlog, however we currently don't have an ETA on when development might start on this. For now, to help us give this the right priority, it would be helpful to see others vote and support this feature, as well as explain their scenarios. |
This item in our backlog, however we currently don't have an ETA on when development might start on this. For now, to help us give this the right priority, it would be helpful to see others vote and support this item. |
Description
Recent release of Azure Service Bus Explorer does provide lot of great functionalities to manage and perform data operations on Service Bus including dead letter queue but I do see two additional features that would make it a viable option VS community managed Service Bus Explorer OSS tool.
Actual Behavior
Expected Behavior
The text was updated successfully, but these errors were encountered: