This is basically a re-invented syslog(3), with a builtin, (supposedly) ephemeral log aggregation service thrown in. It makes some sense for an embedded device, but depending on how restricted your environment is, sending out a UDP packet might be an order of magnitude easier than completing an HTTP transaction. Otherwise, your operating system already has you covered.<p><a href="https://man7.org/linux/man-pages/man3/syslog.3.html" rel="nofollow">https://man7.org/linux/man-pages/man3/syslog.3.html</a> <a href="https://man.openbsd.org/syslog.3" rel="nofollow">https://man.openbsd.org/syslog.3</a> <a href="https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/write-eventlog" rel="nofollow">https://learn.microsoft.com/en-us/powershell/module/microsof...</a> and so on.
... for every environment that has a network connection ;-)<p>Does anybody know a more universal solution where you can have custom transports and that can actually run on any environment? (I'd be targeting an 8-bit microcontroller like a PIC18F25K80, for example, on a CAN bus... and somewhere on the CAN bus there's a custom radio link)