This may not be correct but have you tried to override the systemd-coredump@.service to add an ExecStartPost=your_script_here ?
If I understand correctly, the socket activates the service which is the one to do the dumping itself, so maybe that or a PRE would work for you? Hope it helps, as seems like the simplest way of doing it :D Cheers, Itxaka On Fri, May 9, 2025 at 11:31 AM Johannes Barthel < johannes.bart...@farming-revolution.com> wrote: > Hi, > > we're using an Ubuntu setup where systemd-coredump is set up as the > coredump handler. This is fine, coredumps end up in > /var/lib/systemd/coredump/. We would however like to additionally run our > own event handler (for remote error reporting) in case of a process dumping > core. > > Does systemd-coredump provide any facilities for registering an event > handler for this? Or should we create our own handler, register that as > kernel.core_pattern in sysctl and forward the coredumps to > systemd-coredump? I considered subscribing to the journal and filtering the > coredump event out there, but that might cause unnecessary CPU load and > also the API seems to be kind of broken, I ran into this issue [1]. > > What is the best way of running our custom error reporting script in > addition to systemd-coredump's default behavior? > > Best regards > Johannes > > [1] https://github.com/systemd/python-systemd/issues/98
