Skip to content
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

Add logging #8

Open
Chimstaz opened this issue Dec 2, 2017 · 2 comments
Open

Add logging #8

Chimstaz opened this issue Dec 2, 2017 · 2 comments

Comments

@Chimstaz
Copy link
Owner

Chimstaz commented Dec 2, 2017

Add logging over MQTT on specified channel. It will be good if there will be option to specify level of logging. One proposition is to add in root of configuration packet key "type". If value of type is "Hardware" then do dispatching as it is now. If value of type is "Logging" then add key "Level" with values from set {DEBUG, ERROR, INFO}.

According to #3 prints should utilize new logging mechanic.

@maxiwoj
Copy link
Collaborator

maxiwoj commented Dec 9, 2017

I think it would be great, to have both logging through Serial port (Log level can be set as constant in the code) and logging through mqtt broker for runtime error alerts and remote debugging - this should be possible to set remotely

@Chimstaz
Copy link
Owner Author

Both logging strategy should be included. Maybe Debug level should include option to disable via define in compilation time? It will save some time on release version of application. As stated in #13 only option to publish at the moment is QoS 0. It will be nice, if log message include ID of message to not get lost while debugging when some messages will be dropped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants