Originally the thought was that this enabled property could be used by library and native instrumentation too, but I think those use cases are now covered by the new tracer and meter configs to enable/disable specific instrumentations.

I think the enabled property makes more sense for distros (whether the distro should enable or disable a specific instrumentation).

Maybe we could even go this route for the Spring Boot Starter.

We could start recommending this route for the Java agent users in most cases, while still keeping the ability to completely disable bytecode instrumentation for specific instrumentations where it's needed (e.g. for instrumentations that are expensive to instrument).