This wasn't quite in the documentation, but bears mentioning.
SQLSentry can do many things when a job runs long; send an email, run code, kill the job, etc. In this case, I kill the job and let it restart, but I want people to know this happened so we can make sure the process continues unabated. However, by default the message would've appeared at the very bottom of the message.
Yet I wanted something at the top telling them why this occurred. Patrick at SQLSentry was kind enough to figure it out. First, add the event.
Then you'll edit the message within their Message Editor. The "
Details as per Patrick: