-
Notifications
You must be signed in to change notification settings - Fork 115
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
Device log messages not present on device's "logs" stream #287
Comments
Thanks @kyork-cl. I agree, when using Also I think we should modify the current log format in the server's log to at least show the devices id. @kevinswiber @mdobson Any thoughts on the proposed changes? |
Nope. What would the websocket format look like? Something like: { -- On Fri, Jan 29, 2016 at 10:39 AM, Adam Magaluk [email protected]
|
Also to note the current device log streams do not show up in the the multiplexed websocket when subscribed to |
Whenever a
device.log()
call is made, the output appears in the console and on the servers "logs" topic, but not on the device's "logs" topic.The message object received from the server's "logs" topic also doesn't have an indication of the source of the log, other than the device's name which could be duplicated or not exist.
Could the message that comes from the server "logs" include the ID of the device? Or possible modify the topic to follow the protocol of the WebSocket event stream?
Additionally, could device log messages be available on the device's "logs" stream?
The text was updated successfully, but these errors were encountered: