Skip to content

Commit 65b4ae9

Browse files
committed
add apm errors
1 parent c1b2f81 commit 65b4ae9

File tree

1 file changed

+25
-5
lines changed

1 file changed

+25
-5
lines changed

solutions/observability/apps/errors-2.md

Lines changed: 25 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,31 @@ mapped_urls:
44
- https://www.elastic.co/guide/en/serverless/current/observability-apm-errors.html
55
---
66

7-
# Errors
7+
# Errors [apm-errors]
88

9-
% What needs to be done: Align serverless/stateful
9+
::::{tip}
10+
[Errors](/solutions/observability/apps/errors.md) are groups of exceptions with a similar exception or log message.
11+
::::
1012

11-
% Use migrated content from existing pages that map to this page:
1213

13-
% - [ ] ./raw-migrated-files/observability-docs/observability/apm-errors.md
14-
% - [ ] ./raw-migrated-files/docs-content/serverless/observability-apm-errors.md
14+
*Errors* are groups of exceptions with a similar exception or log message. The **Errors** overview provides a high-level view of the exceptions that APM agents catch, or that users manually report with APM agent APIs. Like errors are grouped together to make it easy to quickly see which errors are affecting your services, and to take actions to rectify them.
15+
16+
A service returning a 5xx code from a request handler, controller, etc., will not create an exception that an APM agent can catch, and will therefore not show up in this view.
17+
18+
:::{image} ../../../images/observability-apm-errors-overview.png
19+
:alt: APM Errors overview
20+
:class: screenshot
21+
:::
22+
23+
Selecting an error group ID or error message brings you to the **Error group**.
24+
25+
:::{image} ../../../images/observability-apm-error-group.png
26+
:alt: APM Error group
27+
:class: screenshot
28+
:::
29+
30+
The error group details page visualizes the number of error occurrences over time and compared to a recent time range. This allows you to quickly determine if the error rate is changing or remaining constant. You’ll also see the top 5 affected transactions—​enabling you to quickly narrow down which transactions are most impacted by the selected error.
31+
32+
Further down, you’ll see an Error sample. The error shown is always the most recent to occur. The sample includes the exception message, culprit, stack trace where the error occurred, and additional contextual information to help debug the issue—​all of which can be copied with the click of a button.
33+
34+
In some cases, you might also see a Transaction sample ID. This feature allows you to make a connection between the errors and transactions, by linking you to the specific transaction where the error occurred. This allows you to see the whole trace, including which services the request went through.

0 commit comments

Comments
 (0)