filename may also be a directory in which case, the filename is generated from the PID and the current date in the specified directory. (FILE, no default value) Note: If a filename is given, '%p' in the filename will be replaced by the PID, and '%t' will be replaced by the time in 'yyyy_MM_dd_HH_mm_ss' format. maxage (Optional) Maximum time to keep the recorded data on disk. This parameter is valid only when the disk parameter is set to true. Note 0s means forever. (INT followed by 's' for seconds 'm' for minutes or 'h' for hours, 0s) maxsize (Optional) Maximum size of the data to keep on disk in bytes if one of the following suffixes is not used: 'm' or 'M' for megabytes OR 'g' or 'G' for gigabytes. This parameter is valid only when the disk parameter is set to 'true'. The value must not be less than the value for the maxchunksize parameter set with the JFR.configure command. (STRING, 0 (no max size)) name (Optional) Name of the recording. If no name is provided, a name is generated. Make note of the generated name that is shown in the response to the command so that you can use it with other commands. (STRING, system-generated default name) path-to-gc-roots (Optional) Flag for saving the path to garbage collection (GC) roots at the end of a recording. The path information is useful for finding memory leaks but collecting it is time consuming. Turn on this flag only when you have an application that you suspect has a memory leak. If the settings parameter is set to 'profile', then the information collected includes the stack trace from where the potential leaking object was allocated. (BOOLEAN, false) settings (Optional) Name of the settings file that identifies which events to record. To specify more than one file, use the settings parameter repeatedly. Include the path if the file is not in JAVA-HOME/lib/jfr. The following profiles are included with the JDK in the JAVA-HOME/lib/jfr directory: 'default.jfc': collects a predefined set of information with low overhead, so it has minimal impact on performance and can be used with recordings that run continuously; 'profile.jfc': Provides more data than the 'default.jfc' profile, but with more overhead and impact on performance. Use this configuration for short periods of time when more information is needed. Use none to start a recording without a predefined configuration file. (STRING, JAVA-HOME/lib/jfr/default.jfc) Event settings and .jfc options can also be specified using the following syntax: jfc-option=value (Optional) The option value to modify. To see available options for a .jfc file, use the 'jfr configure' command. event-setting=value (Optional) The event setting value to modify. Use the form: #= To add a new event setting, prefix the event name with '+'. In case of a conflict between a parameter and a .jfc option, the parameter will take precedence. The whitespace character can be omitted for timespan values, i.e. 20s. For more information about the settings syntax, see Javadoc of the jdk.jfr package. $JFC_OPTIONS Options must be specified using the or = syntax. Multiple options are separated with a $DELIMITER_NAME. Example usage: $SOURCE_NO_ARGUMENTS $SOURCEfilename=dump.jfr $SOURCEfilename=$DIRECTORY $SOURCEdumponexit=true $SOURCEmaxage=1h$DELIMITERmaxsize=1000M $SOURCEsettings=profile $SOURCEdelay=5m$DELIMITERsettings=my.jfc $SOURCEgc=high$DELIMITERmethod-profiling=high $SOURCEjdk.JavaMonitorEnter#threshold=1ms $SOURCE+HelloWorld#enabled=true$DELIMITER+HelloWorld#stackTrace=true $SOURCEsettings=user.jfc$DELIMITERcom.example.UserDefined#enabled=true $SOURCEsettings=none$DELIMITER+Hello#enabled=true Note, if the default event settings are modified, overhead may exceed 1%.