The tracing component provides two configurable settings. For example:

"trace": {
    "directory": "serviceability/trace",
    "levels": {
        "*" : "info",
        "com.foo.*" : "verbose",
        "com.foo.TheClass" : "debug",
        "com.bar.AnotherClass" : "verbose"
    }
}

In this example, the tracing component will write its output to the SERVER_HOME/serviceability/trace directory. The trace component provides five different levels at which trace can be output. These are, in descending order of severity: error, warn, info, debug, and verbose. The configured levels govern what trace is output and what trace is filtered out. Trace levels can be configured for individual classes or for entire packages and package trees. In this example, every class has info level tracing enabled except for those in the com.foo package and its subpackages which have verbose level tracing enabled, com.foo.TheClass which has debug level tracing enabled, and com.bar.AnotherClass which has verbose level tracing enabled. When determining what level of trace is enabled for any given class, the tracing component will use the level of the most specific match, e.g. com.foo.TheClass is a more specific match than com.foo.*. Any classes that are not matched by any of the configured levels will have trace disabled.

The logging component provides a single configurable setting. For example:

"logs": {
    "directory": "serviceability/logs"
}

In this example the logging component will write its output to the SERVER_HOME/serviceability/logs directory.

The dump file component provides a single configurable setting. For example:

"dump": {
    "directory": "serviceability/dump"
}

In this example, the dump file component will write its output to the SERVER_HOME/serviceability/dump directory.