Skip to content
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

Open
rohit3d2003 opened this issue Mar 1, 2023 · 5 comments

Comments

@rohit3d2003
Copy link

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.

  1. Ability to Support staff to filter messages in queue - If we have 1000 of messages in dead letter queue, there should be a way to apply a SQL filter to reduce the result set. This will reduce overall time in finding, triaging and fixing an issue.
  2. Ability to check session state object - If session state object is added to a message (Queue has session enabled), support team should be able to check session state object to help identify what has been done on a particular session so far.

Actual Behavior

  1. Azure Portal Service Bus explorer does not currently allow message filtering and viewing session state object

Expected Behavior

  1. Added functionalities to allow message filtering and viewing session state object via Azure Portal Service Bus Explorer
@EldertGrootenboer
Copy link
Contributor

@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.

@rohit3d2003
Copy link
Author

rohit3d2003 commented Mar 3, 2023

@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

@EldertGrootenboer
Copy link
Contributor

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.

@EldertGrootenboer
Copy link
Contributor

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.

@EldertGrootenboer
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants