[Monitoring] 8.0 Upgrade Assistant

[cachedout]

This is a discussion issue designed to flesh out needed changes for Kibana's Upgrade Assistant for 8.0.

Background

A monitoring cluster that is running a 8.x version of the Stack should have all monitored stack components using Metricbeat collection.

Monitoring Migration Wizard

The Stack Monitoring application has an upgrade wizard which can detect stack components that are sending data via internal collection and which should be migrated to using Metricbeat collection. Using the wizard, a user can be walked through the necessary steps to make the change to Metricbeat collection across their fleet of monitored services.

Upgrade Assistant

There are two principle cases surrounding an upgrade to 8.0 from the monitoring persecptive:

1. A monitored cluster is being upgraded to 8.0 and thus should be using Metricbeat collection if it is not already.

2. A monitoring cluster is being upgraded and monitored components need to be migrated to using Metricbeat collection.

Questions

• How "smart" should the upgrade assistant try to be? Should it try to emulate some/all of the existing behavior of the Migration Wizard?

• Should the migration assistant inform people that after the upgrade they will need to modify a configuration setting in Metricbeat (if they haven't already)?

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[cjcenizal]

@chrisronline I see you're assigned to this -- is this on the roadmap for 7.16?

[chrisronline]

@cjcenizal Sorry, I'm no longer on the team. I will unassign.

[jasonrhodes]

As we are continuing support for internal collection and xpack.enabled standalone Metricbeat collection into 8.0, this ticket is no longer needed.