-
Notifications
You must be signed in to change notification settings - Fork 103
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
split the existing profiles into light/verbose and add a verbose mode for bthport #11
Conversation
Thoughts about keeping the verbose versions of these providers next to the light versions? I'm torn on whether it's more valuable to see all of the Verbose versions grouped together, or whether it's more valuable to see all of the levels of the same provider grouped together. #Resolved Refers to: bluetooth/tracing/BluetoothStack.wprp:1135 in 874af02. [](commit_id = 874af02, deletion_comment = False) |
Keep light and verbose provides next to each other. Then it's easier to see if a provider already has 2 versions |
Moved both the providers next to each other. |
Taking requests for other verbose level providers? I could see the following being useful: Microsoft.Windows.Bluetooth.ForkbeardCore Refers to: bluetooth/tracing/BluetoothStack.wprp:1405 in 874af02. [](commit_id = 874af02, deletion_comment = False) |
i think ill just leave it as is and leave additions to you guys ... i just wanted to get the "template" up so that additions can follow the pattern. |
One more thing : the default profile if you dont specify one seems to be Verbose. I've updated the readme to reflect that. |
This splits the existing Bluetooth profile into 2 modes - a Light mode and a Verbose mode. The Light mode is whatever was there before and will be used in Repro mode etc. The new Verbose mode will allow for changing the verbosity of existing providers - I just added bthport for now.
I tested both profiles and verified that bthport logs are collected at the correct verbosity in each