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
Currently there are 8 dotnet collectors. I believe it would be better to merge these into a single collector, and make it possible to enable/disable "sub-collectors" much like the mssql collector does.
We'll need to consider how we handle the deprecation. I suggest that we handle the translation to the new flag and print a warning for a few versions before dropping the old collector names. For example, having the old flag --collectors.enabled=dotnet_clrjit would have the same effect as --collectors.enabled=dotnet --collector.dotnet.classes-enabled=dotnet (or whatever the flag would be named).
We also need to decide what would be the default sub-collectors. All of them?
The text was updated successfully, but these errors were encountered:
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.
Currently there are 8 dotnet collectors. I believe it would be better to merge these into a single collector, and make it possible to enable/disable "sub-collectors" much like the mssql collector does.
We'll need to consider how we handle the deprecation. I suggest that we handle the translation to the new flag and print a warning for a few versions before dropping the old collector names. For example, having the old flag
--collectors.enabled=dotnet_clrjit
would have the same effect as--collectors.enabled=dotnet --collector.dotnet.classes-enabled=dotnet
(or whatever the flag would be named).We also need to decide what would be the default sub-collectors. All of them?
The text was updated successfully, but these errors were encountered: