github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

[APM] docs: SDH documentation updates (#149359)

Browse source 
## Summary

Two small documentation updates based on feedback in recent SDHs.
This commit is contained in:
Brandon Morelli 2023-01-24 14:30:18 -08:00 • committed by GitHub
parent 4fa3cdcac6
commit 2228086ae6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 9 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/apm/traces.asciidoc
View file

@ -6,7 +6,7 @@ TIP: Traces link together related transactions to show an end-to-end performance
and which services were part of it.
In addition to the Traces overview, you can view your application traces in the <<spans,trace sample timeline waterfall>>.
*Traces* displays your application's entry transactions.
*Traces* displays your application's entry (root) transactions.
Transactions with the same name are grouped together and only shown once in this table.
If you're using <<distributed-tracing,distributed tracing>>,
this view is key to finding the critical paths within your application.

18
docs/apm/troubleshooting.asciidoc
View file

@ -41,20 +41,18 @@ don't forget to check our other troubleshooting guides or discussion forum:
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..."
There are a number of factors that could be at play here.
One important thing to double-check first is your index template.
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**.
*Index templates*
For the APM app to work correctly, an index template must exist for each APM data stream.
By default, {fleet} sets up APM index templates when the APM integration is installed.
Take note that index templates *cannot* be applied retroactively -- they are only applied at index creation time.
More information is available in {apm-guide-ref}/apm-server-configuration.html[Set up and configure].
You can check for the existence of APM index templates in Kibana.
Go to **Stack Management** > **Index Management** > **Index Templates** and search for `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 {ref}/indices-rollover-index.html[rollover API] to target the relevant {apm-guide-ref}/apm-data-streams.html[APM data streams].
[float]
[[troubleshooting-too-many-transactions]]