Jfr::initialize_stage_one consists of multiple steps, but there are no logging related to these steps.
Only overall Jfr::initialize_stage_one success or failure is logged in JfrActivator::on_error.

As a result it takes more time to find out initialization failure cause.
And if someone will try to write tests that will cover different initialization issues, then it would be harder to verify actual failure cause.

I'm suggesting to improve JFR initialization logging.