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

minor: Add further context on device logging from masterclasses #2264

Merged
1 commit merged into from
Apr 28, 2022

Conversation

vipulgupta2048
Copy link
Member

@vipulgupta2048 vipulgupta2048 commented Apr 26, 2022

The great migration of masterclasses begins now.

Context: https://www.flowdock.com/app/rulemotion/i-docs/messages/46759
Signed-off-by: Vipul Gupta (@vipulgupta2048) [email protected]


Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@vipulgupta2048
Copy link
Member Author

@balena-ci I self-certify!

@ghost ghost merged commit 4032090 into master Apr 28, 2022
@ghost ghost deleted the vipul/device-logs-masterclass branch April 28, 2022 05:27
Copy link
Contributor

@zoobot zoobot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are logs stored the same way with local mode and livepush? With persistent logging, does that also store in the same place with local mode?

Copy link
Contributor

@zoobot zoobot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For increasing logs, it would be nice to have exact commands so user can just cp/paste
like

balena ssh device@(baseOS)
vim /etc/systemd/journald.conf

For services, do the logs also go into /etc/systemd/journald.conf of the baseOS or are they on the service docker?

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants