Remote Crash Reporting for Embedded Linux

Hi! First time posting here. Hopefully this is not a stupid question.

I come mostly from a mobile app development background. But recently looking into an indoor appliance project that involves running some flavour of Linux on either something like a Raspberry Pi or even a TX1.

I am very used to remote crash reporting solutions like Sentry or Crashlytics for mobile development. I am wondering about the same thing for embedded Linux. How do one ensure an anomaly free experience once the device gets into the end users' hands? Or is this somehow not a realistic concern?

Please advise. Thanks in advance!

Is this what you had in mind?

https://github.com/aaronovz1/crash-handler

Thanks @Mechanikx for responding!

For iOS/Android development, there are turn-key services (some even for free) that provides a SDK to install into the app. Then it'll just automatically collect any crashes and analytics surrounding anomalies into my cloud account, even if the crashes are happening in production and in the field, without the end-users doing anything. Something like this: https://sentry.io/welcome/

Think if a Smart Thermostat is purchased by thousands of users off Best Buy. How can I as the developer know if there are any problems with my code in the field? Wondering if there are already existing solutions. Thanks!

Ahhh, I see. I should've read you question more carefully

I'm just spitballing here but I wonder if you would need a separate program other than a crash reporting tool? You could have a cron job that executes a program every x amount of time that checks for a crash log. If it exists it would send the report to your email account, using a program like mailx. I have no experience with embedded devices, so I can't say if this is even possible.

Anyways, good luck!

Hey no, the suggestion makes perfect sense, Thanks! Even tho was hoping for something turn-key. Not saying we expect our project to reach high volume of users. But E-mailed reports gets quickly out of hand if a device do reach a good number of people's hands.

Originally Posted by BigFalcon Hey no, the suggestion makes perfect sense, Thanks! Even tho was hoping for something turn-key. Not saying we expect our project to reach high volume of users. But E-mailed reports gets quickly out of hand if a device do reach a good number of people's hands.

I've been battling with Banana Pi A20 boards just stopping, no messages, nothing. In the end, it turns our the kernel team have been working on Power Management so from
kernel 4.15.xx some drivers just stop dead. Disabling the GUI console has done the trick here on both an ASRock J1900 Intel system and the Banana Pi (original).

Alan VK2ZIW