- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.12
- Get started
- Observability AI Assistant
- Application performance monitoring (APM)
- Self manage APM Server
- Data Model
- Features
- How-to guides
- OpenTelemetry integration
- Manage storage
- Configure
- Advanced setup
- Secure communication
- Monitor
- API
- Troubleshoot
- Upgrade
- Release notes
- Known issues
- Logs
- Infrastructure monitoring
- AWS monitoring
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Uptime monitoring
- Real user monitoring
- Universal Profiling
- Alerting
- Service-level objectives (SLOs)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
- Monitor Amazon Web Services (AWS) with Elastic Agent
- Monitor Amazon Web Services (AWS) with Beats
- Monitor Google Cloud Platform
- Monitor a Java application
- Monitor Kubernetes
- Monitor Microsoft Azure with Elastic Agent
- Monitor Microsoft Azure with the Azure Native ISV Service
- Monitor Microsoft Azure with Beats
Switch an Elastic Cloud cluster to the APM integration
editSwitch an Elastic Cloud cluster to the APM integration
editUpgrade the Elastic Stack
editUse the Elastic Cloud console to upgrade the Elastic Stack to version 8.12.2. See the Elasticsearch Service upgrade guide for details.
Switch to Elastic Agent
editAPM 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:
-
In Kibana, navigate to Observability > APM > Settings > Schema.
-
Click Switch to Elastic Agent. Make a note of the
apm-server.ymluser settings that are incompatible with Elastic Agent. Check the confirmation box and click Switch to Elastic Agent.
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 APM app again.
Configure the APM integration
editYou can now update settings that were removed during the upgrade. See Configure 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
editCertain 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.
Congratulations -- you now have the latest and greatest in Elastic APM!
On this page