Run JDK Flight Recorder

JDK Flight Recorder collects diagnostic and profiling data from running Java applications. Run JDK Flight Recorder action will initiate the recording and upload the resulting JFR file to the customer’s tenancy, enabling you to do your own analysis of the recordings.

To enable Run JDK Flight Recorder operations in your fleet, see Enabling Advanced Features. The Run JDK Flight Recorder operation is available for the applications running in a managed instance. Learn more about JDK Flight Recorder.

To run JDK Flight Recorder:

  1. In the Resources section on the fleet details page, navigate to Managed instances. In the Managed instances table, locate the specific managed instance where the application you want to analyze is running.
  2. Click Applications in the Resources section.
  3. In the Resources section on the managed instance details page, navigate to Applications. Select the desired applications by checking the respective boxes in the table. Then, click Actions and choose Run JDK Flight Recorder.
  4. For recording options, you can either:
    • Select from default profiles: choose an pre-defined option from the drop-down menu

      Or

    • Provide Custom flight recorder configuration: the flight recorder configuration has a different format for Java releases prior to JDK 9 and choosing this option will enable you to provide flight recorder configuration for release prior to and after JDK 9.
  5. Provide the period to detect the running applications. The default value will be equal to agent polling interval. You can increase the default value. The maximum is 24 hours.
  6. Provide maximum recording duration of the JFR. The default recording duration is 15 minutes. The minimum value is 1 minute while the maximum is 24 hours.
  7. Provide the maximum recording size for each application that is detected. The default recording size is 500 MB. The minimum value is 1 MB while the maximum is 4096 MB.
  8. Click Start. A Work Request is created for this operation. The progress or status of this operation can be viewed from the Work request module.
Note

  • If the application isn't running during this operation, you'll see a message No events to capture or No reports are available. You'll get a recording only if the application is already running or started during the JFR recording period.
  • JFR generates a recording for the events captured while the application was running.
  • The JFR files are uploaded to the Object storage bucket.