This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« Switch a self-installation to the APM integration Release notes »
Elastic Docs ›Elastic Observability [8.x] ›Application and service monitoring ›Application performance monitoring (APM) ›Upgrade ›Switch to the Elastic APM integration

Switch an Elastic Cloud cluster to the APM integration

edit
Switch an Elastic Cloud cluster to the APM integration
edit
  1. Upgrade the Elastic Stack
  2. Switch to Elastic Agent
  3. Configure the APM integration
  4. Scale APM and Fleet
Upgrade the Elastic Stack
edit

Use the Elastic Cloud console to upgrade the Elastic Stack to version 8.17.0. See the Elasticsearch Service upgrade guide for details.

Switch to Elastic Agent
edit

APM data collection will be interrupted while the migration is in progress. The process of migrating should only take a few minutes.

With a Superuser account, complete the following steps:

  1. In Kibana, navigate to Observability → Applications → Settings → Schema.

    switch to Elastic Agent

  2. Click Switch to Elastic Agent. Make a note of the apm-server.yml user settings that are incompatible with Elastic Agent. Check the confirmation box and click Switch to Elastic Agent.

    Elastic Agent settings migration

Elastic Cloud will now create a Fleet Server instance to contain the new APM integration, and then will shut down the old APM server instance. Within minutes your data should begin appearing in the Applications UI again.

Configure the APM integration
edit

You can now update settings that were removed during the upgrade. See Configure APM Server for a reference of all available settings.

In Kibana, navigate to Management > Fleet. Select the Elastic Cloud Agent Policy. Next to the Elastic APM integration, select Actions > Edit integration.

Scale APM and Fleet
edit

Certain Elasticsearch output configuration options are not available with the APM integration. To ensure data is not lost, you can scale APM and Fleet up and out. APM’s capacity to process events increases with the instance memory size.

Go to the Elastic Cloud console, select your deployment and click Edit. Here you can edit the number and size of each availability zone.

scale APM

Congratulations -- you now have the latest and greatest in Elastic APM!

« Switch a self-installation to the APM integration Release notes »