Following the effort to bring APM Server standalone back to good standing in https://github.com/elastic/apm-dev/issues/917, the instructions in kibana for migrating to fleet managed need an update to reflect that standalone is not deprecated but migrating to fleet managed on ESS is still a reasonable thing to do.
Kibana version: 8.12.1
Following the effort to bring APM Server standalone back to good standing in https://github.com/elastic/apm-dev/issues/917, the instructions in kibana for migrating to fleet managed need an update to reflect that standalone is not deprecated but migrating to fleet managed on ESS is still a reasonable thing to do.
As a first step, let's remove the legacy terminology in https://github.com/elastic/kibana/blob/e2aefd101755db8e600742eb1bc1573f59ac739b/x-pack/plugins/apm/public/components/app/settings/schema/schema_overview.tsx#L119.
Perhaps:
@akhileshpok would a higher level consideration of this flow fit into your efforts on onboarding (or otherwise?)