Many companies in the observability space needs to have highly customized profilers with very specific sampling strategies. One solution, that would also make it easy for folks wanting to integrate existing profilers with JFR, would be to provide a native API for defining and committing JFR events.

The alternative, today, is to emit the information outside of JFR, not sharing the same constant pools, and not being able to take advantage of future improvements in JFR (such as faster stack trace acquisition).

It doesn't even need to be a properly supported API - async get calltrace style brittleness seems to be something the community is ready to roll with.