Even if ApplicationProtocol is reported as Unknown, you should be able to see the underlying transport/network protocols as TCP, UDP, etc.
At this stage, ApplicationProtocol is currently limited to a well-known set of protocols based on standard port mapping logic in the MP. If the port number on the wire data does not follow the standard port number, the application protocol will be shown as Unknown.
It’s on our radar to see how this can be improved in future iterations – we just recently enabled this first version of wiredata and are gathering more feedback on how to evolve it, we are still in the process of documenting it.
(clarification) Be able to define known ports to protocols in the OMS console, if the MP cannot detect that for example, sqlsrvr.exe is listening on 50200, 50201, 50203, etc..
Digging deeper I see that it's SQL traffic. Since we have SQL AG listeners on defined ports, it would be nice to be able to detect those through the MP or in the OMS console.
Nice idea, let’s see how many folks vote on this.
I suspect the Azure Automation DSC feature will be enhanced with a centralize view of all nodes and compliancy, but a view in OMS would be nice as well.
Thanks for your feedback. We’re revising the design of billing experiences in Ibiza and will incorporate this suggestion.