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

Provide an Azure Event Grid event source with ListenerConnected and ListenerDisconnected events #86

Open
dallmair opened this issue Aug 8, 2022 · 2 comments

Comments

@dallmair
Copy link

dallmair commented Aug 8, 2022

Description

With the Hybrid Connections - Get API, we can easily retrieve the number of currently connected listeners of a Hybrid Connection.

It would be great if we could get ListenerConnected and ListenerDisconnected events in Azure Event Grid for this, such that our application can respond to listeners coming up or going down. For example, it would be great if we could show in our application's UI that a listener is currently connected, and have that status display change when the listener disconnects, without polling Azure's REST API all the time.

Actual Behavior

The Azure Service Bus as an Event Grid source article shows that there are currently four events exposed from Azure Service Bus via Azure Event Grid, but none of them related to Hybrid Connections. Also, the Event Grid overview page does not list Azure Relay as a dedicated technology that exposes events via Event Grid.

Expected Behavior

ListenerConnected and ListenerDisconnected events should be available via Azure Event Grid, either via a dedicated Azure Relay event source, or via the existing Azure Service Bus event source.

@dallmair
Copy link
Author

dallmair commented Aug 8, 2022

An alternative could be to have a single ListenerCountChanged event, because all we are actually interested in is the number of active listeners, i.e. if there's none or at least one.

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

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