Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8278740 | 19 | Erik Gahlin | P3 | Resolved | Fixed | b28 |
JVM engineers like to leverage JFR, but not commit to a fully supported event, which includes creating proper metadata, unit tests and update jfc-files.
To mitigate this problem, JFR supports experimental events. For Java events, you can use the @Experimental annotation and native events can use the experimental="true" attribute in metadata.xml. Events that are experimental are not visualized in JMC unless you tick a checkbox in the preference dialog.
To lower the bar further, we could add internal events that will not be visible in the build we ship.
To mitigate this problem, JFR supports experimental events. For Java events, you can use the @Experimental annotation and native events can use the experimental="true" attribute in metadata.xml. Events that are experimental are not visualized in JMC unless you tick a checkbox in the preference dialog.
To lower the bar further, we could add internal events that will not be visible in the build we ship.
- backported by
-
JDK-8278740 JFR: internal events
-
- Resolved
-