The tracing component provides three configurable settings. For example:

    "trace": {
        "directory": "serviceability/trace",
        "defaultLevel": "info",
        "specificLevels": {
            "com.foo.*" : "verbose",
            "com.foo.UnimportantClass" : "info",
            "com.bar.ImportantClass" : "verbose"
        }
    }

In this example, the tracing component will write its output to the $PLATFORM_HOME/serviceabililty/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. A combination of the configured defaultLevel and specificLevels govern what trace is output and what trace is filtered out. Specific trace levels can be configured for individual classes or for entire packages and package trees. In this example, every class in the com.foo package and its subpackages has verbose level tracing enabled except for com.foo.UnimportantClass which has debug 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.UnimportantClass is a more specific match than com.foo.*. Any classes that are not matched by any of the specific levels will have the configured default level of tracing enabled.

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 $PLATFORM_HOME/serviceability/logs directory.

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

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

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