async-profiler.continuous.load-native-library = true - if the tool should load native async-profiler library (turning off disables starter permanently)
It is not true, because autoconfiguration starts unconditionally. It can be easy fixed, but it is an opportunity to review naming convention
In my opinion async-profiler.continuous.load-native-library does not sound like profiler turn on/off permanently.
async-profiler.continuous.enabled sounds. That works for many other autoconfigurations.
But word enabled is already used for something similar to stop-work-file
My proposal is:
async-profiler.continuous.load-native-library -> async-profiler.continuous.enabledasync-profiler.continuous.enabled -> async-profiler.continuous.stopped
I'm OK with that, but that change will not be backward compatible, so I would prefer to do it with 3.0 version, which will be released after async-profiler 3.0 is released.
It is not true, because autoconfiguration starts unconditionally. It can be easy fixed, but it is an opportunity to review naming convention
In my opinion
async-profiler.continuous.load-native-library
does not sound like profiler turn on/off permanently.async-profiler.continuous.enabled
sounds. That works for many other autoconfigurations.But word
enabled
is already used for something similar tostop-work-file
My proposal is:async-profiler.continuous.load-native-library
->async-profiler.continuous.enabled
async-profiler.continuous.enabled
->async-profiler.continuous.stopped