APM settings for Elastic Cloud
Change how Elastic APM runs by providing your own user settings. Starting in Elastic Stack version 8.0, how you change APM settings and the settings that are available to you depend on how you spin up Elastic APM. There are two modes:
- Fleet-managed APM integration
-
New deployments created in Elastic Stack version 8.0 and later will be managed by Fleet.
Check APM configuration reference for information on how to configure Elastic APM in this mode.
- Standalone APM Server (legacy)
-
Deployments created prior to Elastic Stack version 8.0 are in legacy mode. Upgrading to or past Elastic Stack 8.0 will not remove you from legacy mode.
Check Edit standalone APM settings (legacy) and Supported standalone APM settings (legacy) for information on how to configure Elastic APM in this mode.
To learn more about the differences between these modes, or to switch from Standalone APM Server (legacy) mode to Fleet-managed, check Switch to the Elastic APM integration.
User settings are appended to the apm-server.yml
configuration file for your instance and provide custom configuration options.
To add user settings:
Log in to the Elastic Cloud Console.
Find your deployment on the home page or on the Hosted deployments page, then select Manage to access its settings menus.
On the Hosted deployments page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
From your deployment menu, go to the Edit page.
In the APM section, select Edit user settings. (For existing deployments with user settings, you may have to expand the Edit apm-server.yml caret instead.)
Update the user settings.
Select Save changes.
If a setting is not supported by Elastic Cloud Hosted, you will get an error message when you try to save.
Elastic Cloud Hosted generally supports the settings listed in APM documentation under "APM Server binary" when running APM in standalone mode (legacy). For versions before 9, refer to older documentation.
Some settings are intentionally restricted to maintain system stability.
To change logging settings you must first enable deployment logging.