@giangio The Java Melody plugin does give you access to that on its dashboard: https://github.com/javamelody/grails-melody-plugin however, I would be leary of using it in production because of how it is instrumented: https://github.com/javamelody/grails-melody-plugin/issues/68 You might be able to rip off its code: https://github.com/javamelody/javamelody/blob/master/javamelody-core/src/main/java/net/bull/javamelody/SessionListener.java Another option is to move your session to a data store using Spring Sessions: https://docs.spring.io/spring-session/reference/guides/boot-redis.html This is a good option for when you want to start scaling your app, so you can have multiple instances of the app running for load balancing and you don't have to use sticky sessions. I would recommend the Redis version as Redis is fast and works well. There is also a JDBC version, but I would avoid that as it can slow things down but if you decide you have to go that route for some reason make sure your session DB is not the same DB as your app.