[APM] Promote new inventory plugin in APM

[kpatticha]

Summary

Remove the functionality to enable the new experience in APM and replace it with the a link to promote the new inventory. The

Designs

Acceptance criteria

• apm.service.inventory.view local storage should be 'classic'
• Remove the custom_no_data_template in apm (

  kibana/x-pack/plugins/observability_solution/apm/public/components/routing/templates/custom_no_data_template.tsx

  Line 51 in 8d8742f

  defaultMessage: 'Detect and resolve problems with your application',

  )
• Show the promote link only when the observability:entityCentricExperience advanced setting is enabled
• Shows the technical preview icon
• The user can dismiss it

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[iblancof]

@kpatticha, I have a question about the removal of the link to enable the new experience ('Try our new experience!').

In the acceptance criteria, we state that the "Try our new Inventory!" link should only be displayed if apm.service.inventory.view is set to classic. However, the 'Try our new experience!' link is currently showing regardless of whether the view is classic or entity.

Should we remove it regardless of the inventory view? If not, when apm.service.inventory.view is set to entity, should we continue to display 'Try our new experience!'?

[kpatticha]

@iblancof which AC are you referring to?

[kpatticha]

Regarding

when apm.service.inventory.view is set to entity, should we continue to display 'Try our new experience!'?

No, we should not. We'll remove the new service inventory and the user won't have any option to enable/disable this view.

In the acceptance I had added the following to ensure the view is always classic.

• apm.service.inventory.view local storage should be 'classic'

[iblancof]

Oh, I see. So what the AC is actually specifying is that whenever I enter the services inventory, I should set apm.service.inventory.view to classic by default. Am I right?

I initially understood it the other way around, that the new behavior (showing the new link and removing the old one) would only occur if the inventory view mode was set to 'classic', and no changes were necessary otherwise.

@kpatticha, could you please confirm if I got this right?

[kpatticha]

Oh, I see. So what the AC is actually specifying is that whenever I enter the services inventory, I should set apm.service.inventory.view to classic by default. Am I right?

Yes! This is in case a user has already switched to the new view (entity), we need to ensure it always defaults to the classic view, as we're removing the option to switch back. Or you can simply remove the condition where we switch to the new multi signal table. Up to you

I initially understood it the other way around, that the new behavior (showing the new link and removing the old one) would only occur if the inventory view mode was set to 'classic', and no changes were necessary otherwise.

No, we will remove the "new Service" Inventory in apm. The link will basically point to the new inventory plugin

Let me know if you need further clarification.