Skip to content

Commit 804857d

Browse files
kibanamachinekibanamachine
authored
Merge branch 'master' into rk/93436-cloud-urls
2 parents b00a553 + 40c568b commit 804857d

457 files changed

Lines changed: 13175 additions & 6978 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/apm/service-overview.asciidoc‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,8 @@ image::apm/images/traffic-transactions.png[Traffic and transactions]
3838
=== Error rate and errors
3939

4040
The *Error rate* chart displays the average error rates relating to the service, within a specific time range.
41+
An HTTP response code greater than 400 does not necessarily indicate a failed transaction.
42+
<<transaction-error-rate,Learn more>>.
4143

4244
The *Errors* table provides a high-level view of each error message when it first and last occurred,
4345
along with the total number of occurrences. This makes it very easy to quickly see which errors affect

‎docs/apm/transactions.asciidoc‎

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,21 @@ Visualize response codes: `2xx`, `3xx`, `4xx`, etc.
2222
Useful for determining if more responses than usual are being served with a particular response code.
2323
Like in the latency graph, you can zoom in on anomalies to further investigate them.
2424

25+
[[transaction-error-rate]]
2526
*Error rate*::
26-
Visualize the total number of transactions with errors divided by the total number of transactions.
27-
The error rate value is based on the `event.outcome` field and is the relative number of failed transactions.
28-
Any unexpected increases, decreases, or irregular patterns can be investigated further
29-
with the <<errors,errors overview>>.
27+
The error rate represents the percentage of failed transactions from the perspective of the selected service.
28+
It's useful for visualizing unexpected increases, decreases, or irregular patterns in a service's transactions.
29+
+
30+
[TIP]
31+
====
32+
HTTP **transactions** from the HTTP server perspective do not consider a `4xx` status code (client error) as a failure
33+
because the failure was caused by the caller, not the HTTP server. Thus, there will be no increase in error rate.
34+
35+
HTTP **spans** from the client perspective however, are considered failures if the HTTP status code is ≥ 400.
36+
These spans will increase the error rate.
37+
38+
If there is no HTTP status, both transactions and spans are considered successful unless an error is reported.
39+
====
3040

3141
*Average duration by span type*::
3242
Visualize where your application is spending most of its time.

‎docs/user/dashboard/images/lens_advanced_1_1_2.png‎

360 Bytes
Loading

‎docs/user/dashboard/images/lens_advanced_2_2_1.png‎

2.24 KB
Loading

‎docs/user/dashboard/images/lens_advanced_3_1_1.png‎

3.4 KB
Loading

‎package.json‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@
101101
"@elastic/datemath": "link:packages/elastic-datemath",
102102
"@elastic/elasticsearch": "npm:@elastic/elasticsearch-canary@^8.0.0-canary.4",
103103
"@elastic/ems-client": "7.12.0",
104-
"@elastic/eui": "31.7.0",
104+
"@elastic/eui": "31.10.0",
105105
"@elastic/filesaver": "1.1.2",
106106
"@elastic/good": "^9.0.1-kibana3",
107107
"@elastic/maki": "6.3.0",
@@ -203,6 +203,7 @@
203203
"content-disposition": "0.5.3",
204204
"copy-to-clipboard": "^3.0.8",
205205
"core-js": "^3.6.5",
206+
"css-minimizer-webpack-plugin": "^1.3.0",
206207
"custom-event-polyfill": "^0.3.0",
207208
"cytoscape": "^3.10.0",
208209
"cytoscape-dagre": "^2.2.2",

0 commit comments

Comments
 (0)