-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move APM UI documentation to observability-docs with history #3723
base: main
Are you sure you want to change the base?
Conversation
Adding new documentation about the APM UI and definitions of terminology and more. * Images added to docs * Adding Using APM UI page contents * Including new APM UI page * Updated Watcher copy * Copy feedback from @gchaps
Adding content for Machine Learning integration and query bar UI in the Using the APM UI docs.
* docs: initial APM UI updates * docs: using-the-apm-ui updates * more docs updates * quick edits * docs: apply feedback and fix screenshots * docs: incorporate feedback, bold page names * finishing touches and clean up * docs: incorporate feedback from sarah * docs: add feedback * docs: incorporate feedback from gchaps
* [DOCS] Removed ss above spatial references * Removed above from n numeral formatting page
## Summary @gchaps and I met to review text on some APM UI pages. Outcomes: 1. Service **m**ap or Service **M**ap — there is inconsistency in the APM UI with how we refer to Service maps. In some cases, we use title case (Service Map). In others, we use sentence case (Service map). As per the [EUI writing guidelines](https://eui.elastic.co/#/guidelines/writing/guidelines#capitalization), we should use title case for product features. 2. Storage **e**xplorer or Storage **E**xplorer — same story here. We use title case sometimes and sentence case others. We should use title case as this is a product feature. 3. Various text enhancements and changes.
Updates docs for storage explorer. Closes elastic#2960 Closes elastic/kibana#151302 Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary We need a way to decode Android crash's stacktraces so that they can provide meaningful insights to our customers, this is because, due to security reasons, android apps tend to obfuscate their code before publishing it online, making crash reports contain obfuscated names, which don't make any sense before mapping them to the actual source code names. In order to help our customers deobfuscate their stacktraces, we need to allow them to provide us with an R8 map file, which is generated by the code obfuscation tool (R8) at compile time. This map file is needed to later do the deobfuscation process. So these code changes take care of adding a new endpoint that our customers can use to upload their map files, similarly to what's currently available to [RUM Sourcemaps](https://www.elastic.co/guide/en/apm/guide/current/source-map-how-to.html#source-map-rum-upload), the Android map files will be uploaded to ES, using the same index as the one currently used to store RUM Sourcemaps. There's a couple of reasons why a new endpoint to upload android maps is needed instead of re-using the existing RUM Sourcemaps one: * The Sourcemaps upload endpoint has validations in place to check the sourcemap format, which must be a JSON with some expected keys available. Android map files don't have a JSON format, so they are rejected by the sourcemaps endpoint. * Android map files tend to be large in size, just as an example, the map file generated for our [sample app](https://github.com/elastic/opbeans-android) has a size of ~7 MB, so for real apps this number can be larger, which would also cause issues with the RUM upload endpoint since it has a max file limit size of 1 MB. * The RUM upload endpoint contains a parameter (`bundle_filepath `) that doesn't have an equivalent for the android map use case. This PR depends on elastic/kibana#161152 ### Checklist Delete any items that are not applicable to this PR. - [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 ### 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: Søren Louv-Jansen <sorenlouv@gmail.com> Co-authored-by: Brandon Morelli <bmorelli25@gmail.com> Co-authored-by: Katerina Patticha <kate@kpatticha.com>
## Summary Closes elastic/kibana#165393 ### Checklist ### Risk Matrix ### 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)
## Summary Closes elastic#3021.
Closes elastic#3292 ## Summary Updates documentation related to the APM UI based on issues found during the Observability docs bug bash last week. ### Checklist Delete any items that are not applicable to this PR. - [x] @colleenmcginnis [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials: - [x] Clarify that distributed traces aren't the only colorful traces in [Trace sample timeline](https://www.elastic.co/guide/en/kibana/current/spans.html#distributed-tracing) (elastic/kibana@b707c39) - [x] Clarify the implications of the traces table only showing root transactions in [Traces](https://www.elastic.co/guide/en/kibana/current/traces.html) (elastic/kibana@c1de678) - [x] Add beta admonition to APM [Infrastucture](https://www.elastic.co/guide/en/kibana/current/infrastructure.html) page (elastic/kibana@d3bc4a9) - [x] @bmorelli25 review
Closes elastic#3160 ## Summary Adds information on KQL filtering in APM rules. ### Checklist - [x] @colleenmcginnis initial draft - [x] @benakansara review * In what version was this initially added? 8.10.0? - [ ] @colleenmcginnis address feedback, merge
## 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="https://github.com/elastic/kibana/assets/75274611/20277c31-d88c-44ae-b896-1da4223cb392"> Crashes Tab: <img width="1454" alt="Screenshot 2023-10-25 at 10 57 35" src="https://github.com/elastic/kibana/assets/75274611/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>
Part of elastic#3354 (comment) ## Summary `bundle_filepath` should not contain `.map`.
… (#175636) ## Summary Adds fixes that have already been made in the serverless docs. Closes elastic/staging-serverless-observability-docs#181 ### Checklist n/a Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
…vability-docs into moved-content # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had a few comments. The APM UI is very complicated so it's kind of difficult to organize. Not sure if everything I commented is helpful, but I am open to any brainstorming on organizing this content that might come from this.
of information, see <<advanced-queries,Query your data>>. | ||
===== | ||
|
||
[[global-time-range]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Global time range and Service environment filter are appearing on their own pages. Probably need a [float].
[[global-time-range]] | |
[float] | |
[[global-time-range]] |
|
||
The global time range filter in {kib} restricts APM data to a specific time period. | ||
|
||
[[environment-selector]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[[environment-selector]] | |
[float] | |
[[environment-selector]] |
@@ -1,17 +1,47 @@ | |||
[[apm-how-to-guides]] | |||
== How-to guides | |||
== APM UI guides |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if APM UI guides is really intuitive. I would probably expect to find guides that tell me about elements in the UI. Maybe something like APM in-app guides or APM Kibana guides?
@@ -0,0 +1,39 @@ | |||
[[mobile-session-explorer]] | |||
=== Exploring mobile sessions with Discover |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
=== Exploring mobile sessions with Discover | |
=== Explore mobile sessions with Discover |
This allows for the recall of the activities of a specific user during a specific period of time. The best way recall | ||
these data points is using {kibana-ref}/document-explorer.html[Discover]. This guide will explain how to do that. | ||
|
||
=== Viewing sessions with Discover |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is showing as a new page.
[role="screenshot"] | ||
image::./images/apm-transactions-overview.png[Example view of response time distribution] | ||
|
||
[[transaction-duration-distribution]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you want this on the same page as the other transactions. It's currently on it's on page, not sure if it should be or not. I also see it's an element in both Trace samples and Correlations, so maybe that's why these pages are on their own.
|
||
Click and drag to select a latency duration _bucket_ to display up to 500 trace samples. | ||
|
||
[[transaction-trace-sample]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want this on the same page with the other transactions?
[role="screenshot"] | ||
image::./images/apm-logs-tab.png[APM logs tab] | ||
|
||
[[transaction-latency-correlations]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want this on the same page with the other transactions?
@@ -0,0 +1,72 @@ | |||
[[spans]] | |||
=== Trace sample timeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this section kind of redundant with the Trace sample timeline section on the Trace samples page? There's definitely a lot more info here, not sure if this info would be to much to move into the Trace samples page. If we want to keep a separate page, should it be under Transactions, unless this element exists somewhere outside of the individual transactions pages.
@@ -0,0 +1,74 @@ | |||
[[xpack-apm]] | |||
= Navigate the APM UI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section is kind of a beast, but I'm not really sure how I would organize it differently. Seems like you have your top 3 in the Kibana UI with Services, Traces, Dependencies, but most of the headings are service-specific? I wonder if it would make sense to organize the things that are service specific under the services heading to make the initial list under Navigate the APM UI less daunting?
Summary
Preview this PR here
Potential future improvements