Traditionally this is handled by integrating with whatever is tasked with running the BEAM itself. On a traditional VM this might be systemd, or in a more docker oriented deployment structure this would be something like K8s.

Not exactly what you asked; I also specify to the BEAM where to write crash dumps via an environment variable ERL_CRASH_DUMP and have a separate container mounting, sharing, and watching that location to upload the crash dumps to storage so I can easily inspect them.

This isn’t a notification, but still maybe helpful for you.

In any case, setting up a log sink with notifications on key words like “crash dump written” may get you what you’re looking for.

I’ve had apps fail in {apply,{application,start_boot,[stdlib,permanent]}} and {application,start_boot,[kernel,permanent]}} when trying to use custom epmd modules. Just FIY. I don’t think normal apps would experience similar issues, but it is at least possible.