JFR standalone without a separate process

[jodeev]

We want to make it very easy for our existing customers using the Java agent to turn on Real Time Profiling (RTP), provide more options to deploy in container environments, reduce pre-reqs (& align to majority of our customers’ environments) ….

There is a progression of work that will first simplify deployment of RTP for NR Java agent customers and then for customers that opt not to use the Java agent due to performance reasons but want to get the low-overhead insights available from RTP. Each step provides incremental value, and we can opt to stop at any point:

1. JFRD to be compatible with Java 8
2. JFR as an extension to the agent - single process, streamline configuration
3. JFR to be used as a standalone without a separate process

Acceptance Criteria

• JFRD can be deployed like the Java agent - without requiring a separate process - for customers that do not want to use Java agent
• No measurable performance degradation vs previous JFRd standalone installation
• Flamegraphs will work for this standalone JFR deployment deployment option

Aha! Link: https://newrelic.aha.io/features/JAVA-259

[jodeev]

Comment added by Kevyn Ford in Aha! - View

Engineering tasks on track and expecting to complete in April as planned. This will be incorporated into the agent 7.0.0 release, which will be in May (no sooner than 30 days from the public notice on Java 7 EOL given as part of the 6.5.0 release.