I have been trying out the SerilogAnalyser. Unlike the examples in the Readme, I have Custom Logger Interface which has all the log methods.
Since, we are moving to structured logging, we would like to employ some kind of analyzer to verify the code at the compile time to see if the log entries are done correctly.
I used the MessageTemplateFormatMethod attribute approach on my interface methods and it did the job.
I was wondering if we could make the Attribute name itself configurable so that my core code, where the logging interface is defined does not have a dependency on any specific logging framework.
I have been trying out the SerilogAnalyser. Unlike the examples in the Readme, I have Custom Logger Interface which has all the log methods.
Since, we are moving to structured logging, we would like to employ some kind of analyzer to verify the code at the compile time to see if the log entries are done correctly.
I used the
MessageTemplateFormatMethodattribute approach on my interface methods and it did the job.I was wondering if we could make the Attribute name itself configurable so that my core code, where the logging interface is defined does not have a dependency on any specific logging framework.