-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Enhancement] Adding logging to Matter to aid in debuggability #31804
Comments
Let's add the nodeID and/or more context so we can figure out what this is retransmitting to |
We should log what we're trying to discover here. |
Log which MTRDevice (and nodeID) this is for |
Add nodeID to this |
We should log the nodeID here. |
This area in AutoCommissioner (and more down there) to allow us to know which device we're talking to (Could be vid/pid, etc) |
We could, but the message counter can be used to find the original transmission, which has that info...
That information is not currently available there. We could add another initializer which allows passing it in, and update all the callsites that have that info, of course. |
The key here is to have it on a single line, without manual humans reading through logs trying to associate things |
Logging NodeID would be great here too:
Along with all other logging in MTRDevice.mm that begins with "Read attribute work item" |
Reproduction steps
In looking through Matter logging, we could use a little more detail to make it easier to triage networks with multiple devices, and generally associate logs together.
Collecting together a group of "simple" log enhancements that would help here.
The text was updated successfully, but these errors were encountered: