mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 02:09:32 -04:00
33c74aeb03
## Summary This PR adds back the `Errors` tab to mobile apm services under the title `Errors & Crashes`. This new page is split into too sections: errors, and crashes. Error Tab: <img width="1456" alt="Screenshot 2023-10-25 at 10 57 00" src="20277c31-d88c-44ae-b896-1da4223cb392"> Crashes Tab: <img width="1454" alt="Screenshot 2023-10-25 at 10 57 35" src="2b0dea23-cbab-4e68-a14a-c3b14d4bd860"> ### Checklist Delete any items that are not applicable to this PR. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [x] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [x] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [x] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) ### Risk Matrix Delete this section if it is not applicable to this PR. Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release. When forming the risk matrix, consider some of the following examples and how they may potentially impact the change: ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Katerina <kate@kpatticha.com>
36 lines
1.7 KiB
Text
36 lines
1.7 KiB
Text
[role="xpack"]
|
|
[[mobile-errors-crashes]]
|
|
=== Mobile errors and crashes
|
|
|
|
TIP: {apm-guide-ref}/data-model-errors.html[Errors] are groups of exceptions with a similar exception or log message.
|
|
|
|
The *Errors & Crashes* overview provides a high-level view of errors and crashes that APM mobile agents catch,
|
|
or that users manually report with APM agent APIs. Errors and crashes are separated into two tabs for easy differentiation.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
[role="screenshot"]
|
|
image::apm/images/mobile-errors-overview.png[Mobile Errors overview]
|
|
|
|
Selecting an error group ID or error message brings you to the *Error group*.
|
|
|
|
[role="screenshot"]
|
|
image::apm/images/mobile-error-group.png[Mobile Error group]
|
|
|
|
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 "most affected" chart which can be oriented to 'by device' or 'by app version'.
|
|
|
|
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 (when available),
|
|
and additional contextual information to help debug the issue--all of which can be copied with the click of a button.
|
|
|
|
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.
|