At present the weaving injects the line number, class and file into the context block of the log message. We should extend the weaving to also inject the invoking method's signature (or at least name) into the log message context as well.
Under no circumstances should be done with call stack generation. The solution will likely require extending the crosscut rules and possibly require using a flow.
At present the weaving injects the line number, class and file into the context block of the log message. We should extend the weaving to also inject the invoking method's signature (or at least name) into the log message context as well.
Under no circumstances should be done with call stack generation. The solution will likely require extending the crosscut rules and possibly require using a flow.