FR: create "debug" samples

[beriberikix]

During office hours, the community suggested it would be helpful to have samples that help new users as they are getting started with the platform but might run into issues while troubleshooting.

The general idea would be able to test that the different parts of the stack are working. It becomes hard to determine if you're not seeing LightDB Stream data if the cellular modem isn't reliably connecting to a tower. To troubleshoot that specific example, the app could log data locally, publish the the RSSI of the tower, etc. Since it is not intended for production, the sample should err on sending more data and enabling most services (aka a "kitchen sink demo.") It was also suggested that we should have separate samples for Wi-Fi and Cellular since you want different information for each communication medium.

I'd love to use this issue to gather suggestions and requirements!

[chipmc]

Thank you for creating this feature request. I also think that a demo like this would give the new user a chance to interact with the logs and streams functionality of Golioth. For example perhaps the demo could add tags or numeric (generated) data that would let the user get hands on with the CLI and web dashboard capabilities to filter and search the data. All this is to help the user get comfortable with all the features of Golioth and to provide sample code for help getting started on their first "real" project.

[beriberikix]

@ubieda @alvarowolfx feel free to add your ideas if you have a moment!

[ubieda]

Perhaps something to make good use of LightDB would be to trigger remote commands, e.g: query location info on-demand (either GPS location, nearby cell towers or other).

As debug cell info for LightDB Stream, I guess it could make sense to report which cell-IoT technology is used for that connection attempt (is it using NB-IoT or LTE-M?), and if they're using eDRX and/or PSM.