This section describes common problems you might encounter with the APM app. To add to this page, please consider opening a pull request with your proposed changes.

If your issue is potentially related to other components of the APM ecosystem, don’t forget to check our other troubleshooting guides or discussion forum:

Troubleshoot common APM app problemsedit

No APM data foundedit

This section can help with any of the following:

  • Data isn’t displaying in the APM app
  • Data isn’t displaying in the APM app after an upgrade
  • You see a message like "No Services Found",
  • You see errors like "Fielddata is disabled on text fields by default…​"

These problems are likely to be caused by a missing index template or ingest pipeline. By default, Fleet sets up these and other APM assets when the APM integration is installed. Try reinstalling the APM integration by navigating to Integrations > Elastic APM > Manage in Fleet > Settings > Reinstall Elastic APM.

Because assets cannot be applied to indices retroactively, after reinstalling the APM integration you must either wait for the index to rollover or force a rollover. To force a rollover, use the rollover API to target the relevant APM data streams.

Too many unique transaction namesedit

Transaction names are defined in each APM agent; when an APM agent supports a framework, it includes logic for naming the transactions that the framework creates. In some cases though, like when using an APM agent’s API to create custom transactions, it is up to the user to define a pattern for transaction naming. When transactions are named incorrectly, each unique URL can be associated with a unique transaction group—causing an explosion in the number of transaction groups per service, and leading to inaccuracies in the APM app.

To fix a large number of unique transaction names, you need to change how you are using the APM agent API to name your transactions. To do this, ensure you are not naming based on parameters that can change. For example, user ids, product ids, order numbers, query parameters, etc., should be stripped away, and commonality should be found between your unique URLs.

Let’s look at an example from the RUM agent documentation. Here are a few URLs you might find on

// Blog Posts

// Documentation

These URLs, like most, include unique names. If we named transactions based on each unique URL, we’d end up with the problem described above—a very large number of different transaction names. Instead, we should strip away the unique information and group our transactions based on common information. In this case, that means naming all blog transactions, /blog, and all documentation transactions, /guide.

If you feel like you’d be losing valuable information by following this naming convention, don’t fret! You can always add additional metadata to your transactions using labels (indexed) or custom context (non-indexed).

After ensuring you’ve correctly named your transactions, you might still see errors in the APM app related to transaction group limit reached:

The number of transaction groups has been reached. Current APM server capacity for handling unique transaction groups has been reached. There are at least X transactions missing in this list. Please decrease the number of transaction groups in your service or increase the memory allocated to APM server.

You will see this warning if an agent is creating too many transaction groups. This could indicate incorrect instrumentation which will have to be fixed in your application. Alternatively you can increase the memory of the APM server.

Number of transaction groups exceed the allowed maximum(1,000) that are displayed. The maximum number of transaction groups displayed in Kibana has been reached. Try narrowing down results by using the query bar..

You will see this warning if your results have more than 1000 unique transaction groups. Alternatively you can use the query bar to reduce the number of unique transaction groups in your results.

More information

While this can happen with any APM agent, it typically occurs with the RUM agent. For more information on how to correctly set in the RUM agent, see custom initial page load transaction names.

The RUM agent can also set the when observing for transaction events. See apm.observe() for more information.

If your problem is occurring in a different APM agent, the tips above still apply. See the relevant Agent API documentation to adjust how you’re naming your transactions.

Unknown routeedit

The transaction overview will only display helpful information when the transactions in your services are named correctly. If you’re seeing "GET unknown route" or "unknown route" in the APM app, it could be a sign that something isn’t working as it should.

Elastic APM agents come with built-in support for popular frameworks out-of-the-box. This means, among other things, that the APM agent will try to automatically name HTTP requests. As an example, the Node.js agent uses the route that handled the request, while the Java agent uses the Servlet name.

"Unknown route" indicates that the APM agent can’t determine what to name the request, perhaps because the technology you’re using isn’t supported, the agent has been installed incorrectly, or because something is happening to the request that the agent doesn’t understand.

To resolve this, you’ll need to head over to the relevant APM agent documentation. Specifically, view the agent’s supported technologies page. You can also use the agent’s public API to manually set a name for the transaction.

Fields are not searchableedit

In Elasticsearch, index templates are used to define settings and mappings that determine how fields should be analyzed. The recommended index templates for APM are installed by Fleet when the Elastic APM integration is installed. These templates, by default, enable and disable indexing on certain fields.

As an example, some APM agents store cookie values in http.request.cookies. Since http.request has disabled dynamic indexing, and http.request.cookies is not declared in a custom mapping, the values in http.request.cookies are not indexed and thus not searchable.

Ensure an APM data view exists As a first step, you should ensure the correct data view exists. In Kibana, go to Stack Management > Data views. You should see the APM data view—​the default is traces-apm*,apm-*,logs-apm*,apm-*,metrics-apm*,apm-*. If you don’t, the data view doesn’t exist. To fix this, navigate to the APM app in Kibana and select Add data. In the APM tutorial, click Load Kibana objects to create the APM data view.

If creating an APM data view doesn’t solve the problem, see No APM data found for further troubleshooting.

Ensure a field is searchable There are two things you can do to if you’d like to ensure a field is searchable:

  1. Index your additional data as labels instead. These are dynamic by default, which means they will be indexed and become searchable and aggregatable.
  2. Create a custom mapping for the field.

Service Maps: no connection between client and serveredit

If the service map is not showing an expected connection between the client and server, it’s likely because you haven’t configured distributedTracingOrigins.

This setting is necessary, for example, for cross-origin requests. If you have a basic web application that provides data via an API on localhost:4000, and serves HTML from localhost:4001, you’d need to set distributedTracingOrigins: ['https://localhost:4000'] to ensure the origin is monitored as a part of distributed tracing. In other words, distributedTracingOrigins is consulted prior to the APM agent adding the distributed tracing traceparent header to each request.