I have seen that but unfortunately, it doesn't appear to work with an Azure Service Bus.
I have potentially got a workaround that should allow me to use a REST Custom sensor to get this information.
My Solution:
I have created an Azure Function to get the Azure Service Bus information I want, I can then access this function via its URL which should allow me to return the message queue length and report it in PRTG.
I haven't actually tested the response with PRTG yet but I don't see why that won't work.
Would be nice to have a native sensor for this though.
Add comment