Hi, for an embedded device use case I want to trigger a command directly after the creation of a coredump file. My use cases are to collect also the last ~50 lines of log output from journald, then package everything and finally push it to a web storage where my monitoring tools are.
I had a look into the documentation and couldn't find a decent way to do a post-processing like that. Am I missing something or do I have a new feature request? For my use cases, I expect to need the following values for the crashed process to do the above described prost-processing: PID, app binary name, location of the created coredump.
Hi, for an embedded device use case I want to trigger a command directly after the creation of a coredump file. My use cases are to collect also the last ~50 lines of log output from journald, then package everything and finally push it to a web storage where my monitoring tools are. I had a look into the documentation and couldn't find a decent way to do a post-processing like that. Am I missing something or do I have a new feature request? For my use cases, I expect to need the following values for the crashed process to do the above described prost-processing: PID, app binary name, location of the created coredump.