Connecting Zephyr Logging to the Cloud Over Constrained Channels
summary
Shows how Zephyr logs get encoded to CBOR, sent via CoAP over DTLS using the Golioth SDK and stored in LightDB, with one CBOR log per UDP datagram and non‑confirmable posts by default; demonstrates retrieval and formatting with goliothctl and jq; binary hex dumps carry raw bytes so payload grows with dump size; includes dropout detection via message index, discusses batching, selectable acknowledgements, and that about 800 modules already emit logs.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:52The Logging Subsystem in Zephyr
- 3:35Deferred Mode
- 5:00Remote Syslog
- 5:26Flow of How the Log Messages Are Produced in Zephyr Applications
- 9:14Message Counter
- 9:50Possible Output Types of Logging
- 12:27Adding Binary Data to Json
- 14:11Application Protocols
- 17:12Uri Path
- 25:47Configure the App Module To Just Produce Warning Messages and Error Messages
- 26:20Why Is Logging over Internet So Cool
- 30:04Useful Links
related talks
36mConnecting Zephyr Devices at Scale Using Open Source Solutions
36mConnecting Zephyr Devices at Scale Using Open Source Solutions
45mImplementing Network Protocols in Zephyr Project
10mLightning Talk: How to Create an Asset Tracker With Zephyr and Thingsboard In No...
35mLoRa Meets Zephyr
42mFUOTA Using LORAWAN and Zephyr: DFU in the 'Real' World
45mLeveraging Zephyr RTOS for modern embedded systems: a perspective from education and research
42mZbus - the Lightweight and Flexible Zephyr Message Bus