github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 01:38:56 -04:00
Code Issues Projects Releases Packages Wiki Activity

remove links to apm 7.x (#33206)

Browse source
This commit is contained in:
Brandon Morelli 2019-03-15 08:58:20 -07:00 • committed by GitHub
parent 24599135fc
commit b94c83cd47
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/apm/bottlenecks.asciidoc
View file

@ -4,13 +4,13 @@
Elastic APM captures different types of information from within instrumented applications:
* {apm-overview-ref-v}/transaction-spans.html[*Spans*] contain information about a specific code path that has been executed.
* {apm-overview-ref-70}/transaction-spans.html[*Spans*] contain information about a specific code path that has been executed.
They measure from the start to end of an activity,
and they can have a parent/child relationship with other spans.
* {apm-overview-ref-v}/transactions.html[*Transactions*] are a special kind of span that have extra metadata associated with them.
* {apm-overview-ref-70}/transactions.html[*Transactions*] are a special kind of span that have extra metadata associated with them.
You can think of transactions as the highest level of work you’re measuring within a service.
As an example, a transaction could be a request to your server, a batch job, or a custom transaction type.
* {apm-overview-ref-v}/errors.html[*Errors*] contain information about the original exception that occurred or about a log created when the exception occurred.
* {apm-overview-ref-70}/errors.html[*Errors*] contain information about the original exception that occurred or about a log created when the exception occurred.
Each of these information types have a specific page associated with them in the APM UI.
These various pages display the captured data in curated charts and tables that allow you to easily compare and debug your applications.

2
docs/apm/errors.asciidoc
View file

@ -1,7 +1,7 @@
[[errors]]
=== Errors overview
TIP: {apm-overview-ref-v}/errors.html[Errors] are defined as groups of exceptions with matching exception or log messages.
TIP: {apm-overview-ref-70}/errors.html[Errors] are defined as groups of exceptions with matching exception or log messages.
The *Errors* overview provides a high-level view of the error message and culprit,
the number of occurrences, and the most recent occurrence.

2
docs/apm/index.asciidoc
View file

@ -16,7 +16,7 @@ and quickly locate the performance bottlenecks.
* <<apm-ui>>
NOTE: For more information about the components of Elastic APM,
see the {apm-get-started-ref}/overview.html[APM Overview].
see the {apm-overview-ref-70}/overview.html[APM Overview].
--
include::getting-started.asciidoc[]

2
docs/apm/spans.asciidoc
View file

@ -1,7 +1,7 @@
[[spans]]
=== Span timeline
TIP: A {apm-overview-ref-v}/transaction-spans.html[span] is defined as the duration of a single event.
TIP: A {apm-overview-ref-70}/transaction-spans.html[span] is defined as the duration of a single event.
Spans are automatically captured by APM agents, and you can also define custom spans.
Each span has a type and is defined by a different color in the timeline/waterfall visualization.

2
docs/apm/transactions.asciidoc
View file

@ -1,7 +1,7 @@
[[transactions]]
=== Transaction overview
TIP: A {apm-overview-ref-v}/transactions.html[transaction] describes an event captured by an Elastic APM agent instrumenting a service.
TIP: A {apm-overview-ref-70}/transactions.html[transaction] describes an event captured by an Elastic APM agent instrumenting a service.
The APM agents automatically collect performance metrics on HTTP requests, database queries, and much more.
// Clicking *service* brings you to detail of transaction