docs: APM 7.11 updates (#89789) (#89954)

This commit is contained in:
Brandon Morelli 2021-02-02 07:23:22 -08:00 committed by GitHub
parent 4be1693444
commit 9c5e11b07b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 30 additions and 11 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 264 KiB

After

Width:  |  Height:  |  Size: 274 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 318 KiB

After

Width:  |  Height:  |  Size: 272 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 788 KiB

After

Width:  |  Height:  |  Size: 657 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 386 KiB

After

Width:  |  Height:  |  Size: 270 KiB

View file

@ -17,8 +17,8 @@ Response times for the service. You can filter the *Latency* chart to display th
image::apm/images/latency.png[Service latency]
[discrete]
[[service-traffic-transactions]]
=== Traffic and transactions
[[service-throughput-transactions]]
=== Throughput and transactions
The *Throughput* chart visualizes the average number of transactions per minute for the selected service.
@ -62,6 +62,9 @@ each dependency. By default, dependencies are sorted by _Impact_ to show the mos
If there is a particular dependency you are interested in, click *View service map* to view the related
<<service-maps, service map>>.
IMPORTANT: A known issue prevents Real User Monitoring (RUM) dependencies from being shown in the
*Dependencies* table. We are working on a fix for this issue.
[role="screenshot"]
image::apm/images/spans-dependencies.png[Span type duration and dependencies]

View file

@ -17,10 +17,10 @@ If there's a weird spike that you'd like to investigate,
you can simply zoom in on the graph - this will adjust the specific time range,
and all of the data on the page will update accordingly.
*Transactions per minute*::
Visualize response codes: `2xx`, `3xx`, `4xx`, etc.,
and is useful for determining if you're serving more of one code than you typically do.
Like in the Transaction duration graph, you can zoom in on anomalies to further investigate them.
*Throughput*::
Visualize response codes: `2xx`, `3xx`, `4xx`, etc.
Useful for determining if more responses than usual are being served with a particular response code.
Like in the latency graph, you can zoom in on anomalies to further investigate them.
*Error rate*::
Visualize the total number of transactions with errors divided by the total number of transactions.
@ -157,4 +157,4 @@ and solve problems.
[role="screenshot"]
image::apm/images/apm-logs-tab.png[APM logs tab]
// To do: link to log correlation
// To do: link to log correlation

View file

@ -1,14 +1,30 @@
[[troubleshooting]]
== Troubleshoot common problems
== Troubleshooting
++++
<titleabbrev>Troubleshooting</titleabbrev>
++++
If you have something to add to this section, please consider creating a pull request with
your proposed changes in the https://github.com/elastic/kibana[Kibana repository].
This section describes common problems you might encounter with the APM app.
To add to this page, please consider opening a
https://github.com/elastic/kibana/pulls[pull request] with your proposed changes.
Also, check out the https://discuss.elastic.co/c/apm[APM discussion forum].
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:
* {apm-server-ref}/troubleshooting.html[APM Server troubleshooting]
* {apm-dotnet-ref}/troubleshooting.html[.NET agent troubleshooting]
* {apm-go-ref}/troubleshooting.html[Go agent troubleshooting]
* {apm-java-ref}/trouble-shooting.html[Java agent troubleshooting]
* {apm-node-ref}/troubleshooting.html[Node.js agent troubleshooting]
* {apm-py-ref}/troubleshooting.html[Python agent troubleshooting]
* {apm-ruby-ref}/debugging.html[Ruby agent troubleshooting]
* {apm-rum-ref/troubleshooting.html[RUM troubleshooting]
* https://discuss.elastic.co/c/apm[APM discussion forum].
[discrete]
[[troubleshooting-apm-app]]
== Troubleshoot common APM app problems
* <<no-apm-data-found>>
* <<troubleshooting-too-many-transactions>>