13

I'm implementing a logger as an aspect using Spring AOP and Log4J, but I've noticed that the class name in log file is always the LoggerAspect class name, so... is there a way to trace the actual class name in my log?

davioooh
  • 23,742
  • 39
  • 159
  • 250

3 Answers3

16
@Around("execution(* com.mycontrollerpackage.*.*(..))")
public Object aroundWebMethodE(ProceedingJoinPoint pjp) throws Throwable {      
    String packageName = pjp.getSignature().getDeclaringTypeName();
    String methodName = pjp.getSignature().getName();
    long start = System.currentTimeMillis();
    if(!pjp.getSignature().getName().equals("initBinder")) {
       logger.info("Entering method [" + packageName + "." + methodName +  "]");
    }
    Object output = pjp.proceed();
    long elapsedTime = System.currentTimeMillis() - start;
    if(!methodName.equals("initBinder")) {
       logger.info("Exiting method [" + packageName + "." + methodName + "]; exec time (ms): " + elapsedTime);
    }
    return output;
}
atrain
  • 9,139
  • 1
  • 36
  • 40
  • This even works for proxied classes (the non-proxied name is shown in the log message). – jolo Sep 06 '17 at 14:49
13

this is easier:

pjp.getTarget().getClass()
Ivan Velykorodnyy
  • 401
  • 3
  • 11
4

Use : pjp.getTarget().getClass().getCanonicalName()

Also, to add logs at class level of which method is being exexuted instead using logger of advice class, use class level logger within advice method, as below

Logger logger = Logger.getLogger(pjp.getTarget().getClass().getCanonicalName());
Nitul
  • 997
  • 12
  • 35
  • This is not a good practice i.e. asking for logger object for every advice method call. – Mohit May 21 '20 at 12:21
  • 1
    Good point @Mohit, but Slf4J has an implementation of having all the logger objects cached, so it's not a significant overhead. – varra Jan 11 '23 at 12:58