That line IS the syslog message...
<86> refers to the syslog priority the message came in with (both 6 &
 is the processID of the sshd process on the server that sent the syslog message.
I may be wrong, but I don't think The Dude can do exactly what you want without some additional help.
As far as I can tell, none of these fields: [probe.name], [Device.Name], [Service.Status] has anything to do with a syslog message... They are very likely fields if your notification came from another source (like a Dude monitored device goes down), but not from syslog.
Once the Dude rececives a syslog message, it is separated into three fields... Time (the time the message was received), Address (the address that sent the syslog message), and Event (the actual message).
IF there are dude variables for these, I'd think they'd be [Syslog.Time], [Syslog.Address], and [Syslog.Event]... I'm not in a place I can test that, and I haven't seen any such reference to those variables, so I I seriously doubt it.
If you want to change the behavior, I think you're going to have to create a notification with the type "execute on server", the write a script to parse, reformat, then e-mail out the data..
Documentation is a bit lacking on some things in The Dude, like the "execute on server"... I'm not exactly sure how you specify within the notification exactly *what* you're going to execute on the server, nor how you pass the message to the script...