Log4net.Appender.Serilog | Serilog appender for log4net

As a step in switching from NLog to Serilog, I want to redirect the standard wiring underlying standard invocations of NLog's LogManager.GetLogger(name) to Bridge any code logging to NLog to forward immediately to the ambient Serilog Log.Logger - i.e. I want to just one piece of config that simply forwards the message, without buffering as Log4net.Appender.Serilog does for Log4net.

Can anyone concoct or point me to a canonical snippet that does this correctly and efficiently please? Requirements I can think of:

• Maintain the level, i.e. nlog.Warn should be equivalent to serilog.Warning
• It's ok for Serilog to generate the time anew
• materializing the message in the appender - i.e., there's no need to maintain any properties associated with the 'message' (the LogEvent in Serilog terms)
• no buffering
• I don't need any other NLog Target to be used (i.e. mutating/deleting the message would be fine)