Profiler Troubleshooting
New announcements from Dash: Incident Management, Continuous Profiler, and more! New announcements from Dash!

Profiler Troubleshooting

Missing profiles in the profile search page

If you’ve configured the profiler and don’t see profiles in the profile search page, turn on debug mode and open a support ticket with debug files and the following information:

  • Operating system type and version (for example, Linux Ubuntu 14.04.3)
  • Runtime type, version, and vendor (for example, Java OpenJDK 11 AdoptOpenJDK)

Java 8 support

The following OpenJDK 8 vendors are supported for Continuous Profiling because they include JDK Flight Recorder in their latest versions:

VendorJDK version that includes Flight Recorder
Azulu212 (u262 is recommended)
Amazon (Corretto)u262
Bell-Soft (Liberica)u262
Upstream buildsu272

If your vendor is not on the list, open a support ticket, we can let you know if we’re planning to support it or if we already offer beta support.

Removing sensitive information from profiles

If your system properties contain sensitive information such as user names or passwords, turn off the system property event by creating a jfp override template file with jdk.InitialSystemProperty disabled:



Exceptions overwhelming the profiler

The Datadog exception profiler will normally have a very small footprint and overhead. But if a lot of exceptions are created and thrown, it can cause significant overhead for the profiler. This can happen, for example, when you use exceptions for control flow. If you have an unusually high exception rate, temporarily turn off exception profiling until you’ve had a chance to fix what’s causing them.

To disable exception profiling, start the tracer with the -Ddd.integration.throwables.enabled=false JVM setting.

Remember to turn this setting back on after you’ve returned to a more typical rate of exceptions.

Further Reading

Additional helpful documentation, links, and articles: