The title says it all really, I would like to be able to route my messages based on a topic rather than the class that posts the message. For example, I have an audit requirement and a log requirement for the same class.
When I start/stop a given job, I want to audit that, but I also want to record job progress within the class via logging. I see my audit and logging sinks as being different and backed by different storage. How can I model this in Log4Net? Also, is it possible to include meta data with the log message? I could do with appending an XML payload to be digested by the sink, if that's possible. Cheers, Steve -- View this message in context: http://www.nabble.com/Newbie%3A-Does-Log4Net-have-the-concept-of-%22Topics%22-and%2C-if-so%2C-can-I-route-messages-based-on-topic-rather-than-%22Class%22-hierarchy--tf4683548.html#a13383219 Sent from the Log4net - Users mailing list archive at Nabble.com.
