maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

docs: add more info on http transactions/span (#95598) (#95669)

Browse source
This commit is contained in:
Brandon Morelli 2021-03-29 08:47:50 -07:00 committed by GitHub
parent b205abf2bc
commit 491f6735ce
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 16 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/apm/service-overview.asciidoc
View file

@ -38,6 +38,8 @@ image::apm/images/traffic-transactions.png[Traffic and transactions]
=== Error rate and errors
The *Error rate* chart displays the average error rates relating to the service, within a specific time range.
An HTTP response code greater than 400 does not necessarily indicate a failed transaction.
<<transaction-error-rate,Learn more>>.
The *Errors* table provides a high-level view of each error message when it first and last occurred,
along with the total number of occurrences. This makes it very easy to quickly see which errors affect

18
docs/apm/transactions.asciidoc
View file

@ -22,11 +22,21 @@ 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.
[[transaction-error-rate]]
*Error rate*::
Visualize the total number of transactions with errors divided by the total number of transactions.
The error rate value is based on the `event.outcome` field and is the relative number of failed transactions.
Any unexpected increases, decreases, or irregular patterns can be investigated further
with the <<errors,errors overview>>.
The error rate represents the percentage of failed transactions from the perspective of the selected service.
It's useful for visualizing unexpected increases, decreases, or irregular patterns in a service's transactions.
+
[TIP]
====
HTTP **transactions** from the HTTP server perspective do not consider a `4xx` status code (client error) as a failure
because the failure was caused by the caller, not the HTTP server. Thus, there will be no increase in error rate.
HTTP **spans** from the client perspective however, are considered failures if the HTTP status code is ≥ 400.
These spans will increase the error rate.
If there is no HTTP status, both transactions and spans are considered successful unless an error is reported.
====
*Average duration by span type*::
Visualize where your application is spending most of its time.