C1 is unfortunately quite the school book example of using configuration over convention. Its not possible to define much at runtime, it all has to be done through configuration files.
When that's said, its easy enough to write your own TraceListener like napernik mentioned, there is a Loggly-package here you can look at https://bitbucket.org/burningice/compositec1contrib/src/1bb2cf83a4729fef6663ad1aba1d7f49de4c9280/Loggly/LogglyTraceListener.cs?at=default.
If you do favor runtime IoC and DI, then this is a project you should look at, and feel free to contribute as you see fit https://bitbucket.org/actoas/composite-c1-acto-build-ioc-and-di/commits/all. Have a ServiceContainer infrastructure in place makes it possible to make the components replaceable, one by one.
When that's said, its easy enough to write your own TraceListener like napernik mentioned, there is a Loggly-package here you can look at https://bitbucket.org/burningice/compositec1contrib/src/1bb2cf83a4729fef6663ad1aba1d7f49de4c9280/Loggly/LogglyTraceListener.cs?at=default.
If you do favor runtime IoC and DI, then this is a project you should look at, and feel free to contribute as you see fit https://bitbucket.org/actoas/composite-c1-acto-build-ioc-and-di/commits/all. Have a ServiceContainer infrastructure in place makes it possible to make the components replaceable, one by one.