Error messages often contain "variable" parts (a username, a process ID, a timestamp etc); these make it hard to group messages in interfaces like fatalmonitor and thus to spot frequent issues early. PSR-3 logging provides a nice mechanism to abstract these variable part away: one can pass the logger a message template like $logger->log( 'DB error when {user} tried to save {page}', array( 'user' => $username, 'page' => $pageId ) ); and the variables will be interpolated by Monolog.
We should store the message templates in a separate field, and use them in fatalmonitor for faceted search.