Manage your APM Server (versions before 7.13)

Manage your APM Server (versions before 7.13)edit

For deployments that are version 6.3 and later, you have the option to add an Application Performance Monitoring (APM) Server to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. The APM data is automatically available in Kibana for your searching and visualizing needs. For more information regarding Elastic APM, check www.elastic.co/solutions/apm.

As part of provisioning, the APM Server is already configured to work with Elasticsearch and Kibana. At the end of provisioning, you are shown the secret token to configure communication between the APM Server and the backend APM Agents. The secret token can be found and reset on the APM & Fleet page of the deployment menu (it is not managed in the user override settings). The APM Agents get deployed within your services and applications.

From the deployment APM page you can also:

  • Get the URL to complete the agent configuration.
  • Use the elastic credentials to go to the APM area of Kibana. Step by step instructions to configure a variety of agents are available right in Kibana. After that, you can use the pre-built, dedicated dashboards and the APM tab to visualize the data that is sent back from the APM Agents.
  • Reset the secret token.

    Resetting the token disrupts your APM service and restarts the server. When the server restarts, you’ll need to update all of your agents with the new token.

  • Access the APM logs and metrics.
  • Stop and restart your APM Server.
  • Upgrade your APM Server version if it is out of sync with your Elasticsearch cluster.
  • Fully remove the APM Server, delete it from the disk, and stop the charges.

Starting with stack version 7.13, the APM Server is accompanied by a Fleet Server. Check Manage your APM and Fleet Server for details.