You have the option to deploy APM in the same Elastic Cloud deployment where you are running Enterprise Search, but this is not mandatory. If desire, you can set up a new Elastic Cloud deployment to deploy APM and integrate with an existing Enterprise Search deployment.
If your Enterprise Search deployment is on-premises, you can either install a new Elastic APM Server in your infrastructure, use an existing Elastic APM Server, or create an Elastic Cloud deployment (see “Elastic Cloud” section in Step 1 above) with APM & Fleet enabled.
Enterprise Search’s embedded APM Ruby agent is compatible with APM server >= version 6.5.
If you are already using the Elastic APM solution for performance monitoring of other applications and have an APM Server available, skip to Step 2.
If you are installing a new APM Server in your infrastructure, install the latest APM Server (follow only Step 1: Spin up the Elastic Stack in the Self-managed tab) and connect it to a new or existing Elasticsearch cluster. Install a Kibana instance to connect to the Elasticsearch cluster so you can visualize (“Self-managed” tab) the resulting APM data in Step 4.
Step 2: Copy the APM Server endpoint and secret token
Once APM & Fleet is enabled in your Elastic Cloud deployment, copy the APM endpoint and secret token from the Cloud user console. You will use these values in Step 3 in the Enterprise Search configuration.
Read more here: Source link