Thinking about this some more, I think I'd really rather have the errors propagate up to the caller.   heka supports raven and sentry for stacktrace support and I think it makes sense for CEF messages to fire off for discrete security related events.

In the case that the node-cef library itself is called incorrectly, I think we should hook into the raven client to send a stacktrace to Sentry so that we can see the error in the application.  If we really do have a case where a developer accidentally passes in the wrong type to the the CEF logger, I'd like to treat that as an actual error and have raven hand off a full stackframe to sentry for later analysis.