Class loader names are being added to JDK 9, see
http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2016-October/021690.html

Event-based tracing should allow for tracing Class Loader instances (not just types), this would allow for associating the newly added class loader names with exisiting data.

Example output suggestion:

// existing output

Class Load: [Loaded Class = java/lang/Exception, Defining Class Loader = NULL, Initiating Class Loader = jdk/internal/loader/ClassLoaders$AppClassLoader]
Class Load: [Loaded Class = java/lang/Class, Defining Class Loader = NULL, Initiating Class Loader = jdk/internal/loader/ClassLoaders$AppClassLoader]
Class Load: [Loaded Class = java/util/Vector, Defining Class Loader = NULL, Initiating Class Loader = jdk/internal/loader/ClassLoaders$AppClassLoader]
Class Load: [Loaded Class = java/lang/Integer, Defining Class Loader = NULL, Initiating Class Loader = jdk/internal/loader/ClassLoaders$AppClassLoader]

// suggested updated output

Class Load: [Loaded Class = java/lang/Exception, Defining Class Loader = NULL, Initiating Class Loader = name=app class=jdk/internal/loader/ClassLoaders$AppClassLoader]
Class Load: [Loaded Class = java/lang/Class, Defining Class Loader = NULL, Initiating Class Loader = name=app class=jdk/internal/loader/ClassLoaders$AppClassLoader]
Class Load: [Loaded Class = java/util/Vector, Defining Class Loader = NULL, Initiating Class Loader = name=app class=jdk/internal/loader/ClassLoaders$AppClassLoader]
Class Load: [Loaded Class = java/lang/Integer, Defining Class Loader = NULL, Initiating Class Loader = name=app class=jdk/internal/loader/ClassLoaders$AppClassLoader]