thanks for the guidance @armor.
Yeah I know most of the info is in the console but thinking I'd add it to my SQL table as well just to quickly look across all devices or if I needed to access any piece of info from any application I can easily do it if it exists in a SQL table. Probably a way to do it via a Particle API as well I suppose instead of trying to manage some of this in my own offline table.
The main item that came to mind that even made me think of asking the question was the Sara-R410M FW version. As I had one device in the past lock up likely due to the 124 day issue. So I'm a bit sensitive to it. The device itself publishes mostly raw sensor values and then I scale it in the cloud vs locally on device.
I am using this as an external RTC for Watchdog and deep power down upon lack of connectivity: https://github.com/particle-iot/app-notes/tree/master/AN023-Watchdog-Timers
and with every reset event I do capture the reset reason and if the watchdog did the reset. The device publishes this info the next time it connects and I save it to a SQL table. This should give me a log of all reset events across any device and the reason for the reset but doesn't provide any sort of trace.
- How would I do this? This seems like it would be good information to capture as part of capturing every reset event. Right now I just capture the reason for different reset conditions but I don't capture the trace. Is there an example of how to do this? Is this just having a retained memory integer value and then keep updating the value of the integer throughout the firmware? Then capture it at the start of setup()? Or how would I do this?