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

Update APM links (#156460)

Browse source 
This PR updates three APM links. For the failing links in
https://github.com/elastic/apm-server/pull/10560.
This commit is contained in:
Brandon Morelli 2023-05-02 18:42:18 -07:00 • committed by GitHub
parent 12277ac0b3
commit 72c5d5286a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/apm/troubleshooting.asciidoc
View file

@ -93,8 +93,8 @@ Instead, we should strip away the unique information and group our transactions
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 {apm-guide-ref}/metadata.html#labels-fields[labels] (indexed) or
{apm-guide-ref}/metadata.html#custom-fields[custom context] (non-indexed).
You can always add additional metadata to your transactions using {apm-guide-ref}/data-model-metadata.html#data-model-labels[labels] (indexed) or
{apm-guide-ref}/data-model-metadata.html#data-model-custom[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:
@ -167,7 +167,7 @@ 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 {apm-guide-ref}/metadata.html[labels] instead.
1. Index your additional data as {apm-guide-ref}/data-model-metadata.html[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.