You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, in Azure SDK 2.6 diagnostics through code is entirely deprecated (SignalRDiagnosticHelper class) and everything must be configured in xml file diagnostics.wadcfgx.
Does it mean that it is enough simply to move definitions of performance counters to the xml configuration file? If so, how should we be with dynamic category names? Or can this still lead to troubles due to diagnostics monitor starting before the role starts?
P.S. It would be also nice to have the asp.net article updated with the latest SDK 2.6 changes.
The text was updated successfully, but these errors were encountered:
I did some reviewing of the doc. It's quite out of date. I can assemble an outline for building a new one. The dynamic category names are a small problem, but you can register for all of instances of the SignalR counters by using \SignalR(*)\[Counter Name] as the path. For example \SignalR(*)\Connections Current.
There is a good article explaining how to enable SignalR performance counters on Azure web roles:
Using SignalR Performance Counters in an Azure Web Role
However, in Azure SDK 2.6 diagnostics through code is entirely deprecated (SignalRDiagnosticHelper class) and everything must be configured in xml file diagnostics.wadcfgx.
Does it mean that it is enough simply to move definitions of performance counters to the xml configuration file? If so, how should we be with dynamic category names? Or can this still lead to troubles due to diagnostics monitor starting before the role starts?
P.S. It would be also nice to have the asp.net article updated with the latest SDK 2.6 changes.
The text was updated successfully, but these errors were encountered: