Skip to content
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

[One Discover] Display stacktrace in the logs overview tab #204521

Merged
merged 45 commits into from
Jan 22, 2025

Conversation

gbamparop
Copy link
Contributor

@gbamparop gbamparop commented Dec 17, 2024

📓 Summary

Adds a new section to the overview tab in the log details flyout in Discover to display stacktrace information for logs and exceptions.

In a follow-up, the stacktrace could be moved to a new tab in the log details flyout and actions can be added to the stacktrace (and quality) icons in the document table to open the relevant sections in the flyout.

Closes #190460

APM - Log stacktrace (library frames)

image

APM - Exception (with cause)

image

APM - Exception (simple stacktrace)

image

Apache Tomcat Integration (Catalina) - Stacktrace

image

📝 Notes for reviewers

  • The @kbn/apm-types package was marked as platform / shared as it's being used by the unified_doc_viewer
  • The code used to render stacktraces in APM was moved into a new @kbn/event-stacktrace package as it is reused in the unified_doc_viewer
  • The code used to render metadata table in APM was moved into a new @kbn/key-value-metadata-table package

🧪 Testing instructions

The deployed environments have sample logs that can be used (time range: Jan 1, 2025 - now). For a local setup, please follow the instructions below:

  1. Ingest sample logs with stacktraces (gist). Please note that these are test data and some fields that are not used by stacktraces might not be consistent
  2. View relevant logs in Discover (Query: service.name: "synth-node-0" OR apache_tomcat :*, Time range: Jan 1, 2025 - now)

@gbamparop gbamparop added release_note:skip Skip the PR/issue when compiling release notes backport:skip This commit does not require backporting labels Dec 17, 2024
@gbamparop
Copy link
Contributor Author

/ci

@gbamparop gbamparop force-pushed the discover-logs-stacktrace branch from e11d28d to b41227d Compare December 17, 2024 08:57
@gbamparop
Copy link
Contributor Author

/ci

@gbamparop
Copy link
Contributor Author

/ci

@gbamparop
Copy link
Contributor Author

/ci

@gbamparop
Copy link
Contributor Author

/ci

@gbamparop
Copy link
Contributor Author

/oblt-deploy

@gbamparop
Copy link
Contributor Author

/ci

@gbamparop
Copy link
Contributor Author

/ci

@elasticmachine
Copy link
Contributor

elasticmachine commented Jan 21, 2025

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
apm 1695 1697 +2
unifiedDocViewer 236 277 +41
total +43

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id before after diff
@kbn/discover-utils 228 229 +1
@kbn/event-stacktrace - 18 +18
@kbn/key-value-metadata-table - 10 +10
total +29

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
apm 4.0MB 4.0MB +22.0B
discover 844.0KB 844.3KB +258.0B
logsExplorer 222.5KB 222.5KB +36.0B
unifiedDocViewer 124.1KB 148.5KB +24.4KB
total +24.7KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
logsExplorer 26.7KB 26.8KB +111.0B
Unknown metric groups

API count

id before after diff
@kbn/discover-utils 278 279 +1
@kbn/event-stacktrace - 18 +18
@kbn/key-value-metadata-table - 10 +10
total +29

ESLint disabled line counts

id before after diff
@kbn/event-stacktrace - 2 +2
@kbn/key-value-metadata-table - 1 +1
total +3

Total ESLint disabled count

id before after diff
@kbn/event-stacktrace - 2 +2
@kbn/key-value-metadata-table - 1 +1
total +3

History

Copy link
Contributor

@tonyghiani tonyghiani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for applying the changes!

Copy link
Member

@jennypavlova jennypavlova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Obs UX infra Services changes LGTM

Copy link
Contributor

@jughosta jughosta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Data Discovery changes LGTM 👍

Would it be possible to display stacktrace in the grid too? The current cells are not able to show this information in a readable way.

Some options:

  • improve cells rendering but I guess it's tricky as stacktrace data is split in multiple fields, right?
  • make the row button actionable: show the stacktrace in a popover or open the Logs Overview tab on click.
Screenshot 2025-01-21 at 17 46 39

Copy link
Contributor

@TinaHeiligers TinaHeiligers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no-op newline change in manifest LGTM

@gbamparop
Copy link
Contributor Author

gbamparop commented Jan 22, 2025

Would it be possible to display stacktrace in the grid too? The current cells are not able to show this information in a readable way.

@jughosta These are good ideas, thanks for sharing!

  • improve cells rendering but I guess it's tricky as stacktrace data is split in multiple fields, right?

Displaying more complex APM stacktraces requires data from several subfields, however, error.stack_trace is an ECS field (wildcard) with error.stack_trace.text as match_only_text that we could possibly use to render a formatted stacktrace in a cell. I'll create a follow-up issue and add it to the list.

  • make the row button actionable: show the stacktrace in a popover or open the Logs Overview tab on click.

We have previously discussed it with the team, I've updated #190670 to include an action for the stacktrace section in addition to the quality section

@gbamparop gbamparop added backport:version Backport to applied version labels v9.0.0 v8.18.0 release_note:enhancement and removed backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes labels Jan 22, 2025
@gbamparop gbamparop merged commit 368475e into elastic:main Jan 22, 2025
19 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/12912247501

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.x Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 204521

Questions ?

Please refer to the Backport tool documentation

@davismcphee
Copy link
Contributor

improve cells rendering but I guess it's tricky as stacktrace data is split in multiple fields, right?

I really like this idea too, and I think we could do it even if the data is split across fields. We have access to the full record when rendering a cell value, so we could use those other fields when rendering error.stack_trace for a complex view, and fall back to something simpler when some are missing or only error.stack_trace is available.

viduni94 pushed a commit to viduni94/kibana that referenced this pull request Jan 23, 2025
…04521)

## 📓 Summary
Adds a new section to the overview tab in the log details flyout in
Discover to display stacktrace information for logs and exceptions.

In a follow-up, the stacktrace could be moved to a new tab in the log
details flyout and actions can be added to the stacktrace (and quality)
icons in the document table to open the relevant sections in the flyout.

Closes elastic#190460

### APM - Log stacktrace (library frames)
<img width="1470" alt="image"
src="https://github.com/user-attachments/assets/8991f882-d329-4bc5-aa37-424576bcee72"
/>

### APM - Exception (with cause)
<img width="1476" alt="image"
src="https://github.com/user-attachments/assets/cfbf24a7-6f82-48f1-b275-5aac977411ac"
/>

### APM - Exception (simple stacktrace)
<img width="1474" alt="image"
src="https://github.com/user-attachments/assets/fc0306c4-5fcd-4b74-bb0d-c1784a48d677"
/>

### Apache Tomcat Integration (Catalina) - Stacktrace
<img width="1472" alt="image"
src="https://github.com/user-attachments/assets/281f1822-faea-4e2d-9515-c11a9ee12f50"
/>

## 📝 Notes for reviewers
- The `@kbn/apm-types` package was marked as platform / shared as it's
being used by the
[unified_doc_viewer](https://github.com/elastic/kibana/blob/main/src/plugins/unified_doc_viewer/kibana.jsonc)
- The code used to render stacktraces in APM was moved into a new
`@kbn/event-stacktrace` package as it is reused in the
`unified_doc_viewer`
- The code used to render metadata table in APM was moved into a new
`@kbn/key-value-metadata-table` package

## 🧪 Testing instructions
The deployed environments have sample logs that can be used (time range:
Jan 1, 2025 - now). For a local setup, please follow the instructions
below:

1. Ingest sample logs with stacktraces
([gist](https://gist.github.com/gbamparop/0da21ca7f65b24c4a9c071ce9e9b97b0)).
Please note that these are test data and some fields that are not used
by stacktraces might not be consistent
2. View relevant logs in Discover (Query: `service.name: "synth-node-0"
OR apache_tomcat :*`, Time range: Jan 1, 2025 - now)

---------

Co-authored-by: kibanamachine <[email protected]>
@gbamparop
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

gbamparop added a commit to gbamparop/kibana that referenced this pull request Jan 23, 2025
…04521)

## 📓 Summary
Adds a new section to the overview tab in the log details flyout in
Discover to display stacktrace information for logs and exceptions.

In a follow-up, the stacktrace could be moved to a new tab in the log
details flyout and actions can be added to the stacktrace (and quality)
icons in the document table to open the relevant sections in the flyout.

Closes elastic#190460

### APM - Log stacktrace (library frames)
<img width="1470" alt="image"
src="https://github.com/user-attachments/assets/8991f882-d329-4bc5-aa37-424576bcee72"
/>

### APM - Exception (with cause)
<img width="1476" alt="image"
src="https://github.com/user-attachments/assets/cfbf24a7-6f82-48f1-b275-5aac977411ac"
/>

### APM - Exception (simple stacktrace)
<img width="1474" alt="image"
src="https://github.com/user-attachments/assets/fc0306c4-5fcd-4b74-bb0d-c1784a48d677"
/>

### Apache Tomcat Integration (Catalina) - Stacktrace
<img width="1472" alt="image"
src="https://github.com/user-attachments/assets/281f1822-faea-4e2d-9515-c11a9ee12f50"
/>

## 📝 Notes for reviewers
- The `@kbn/apm-types` package was marked as platform / shared as it's
being used by the
[unified_doc_viewer](https://github.com/elastic/kibana/blob/main/src/plugins/unified_doc_viewer/kibana.jsonc)
- The code used to render stacktraces in APM was moved into a new
`@kbn/event-stacktrace` package as it is reused in the
`unified_doc_viewer`
- The code used to render metadata table in APM was moved into a new
`@kbn/key-value-metadata-table` package

## 🧪 Testing instructions
The deployed environments have sample logs that can be used (time range:
Jan 1, 2025 - now). For a local setup, please follow the instructions
below:

1. Ingest sample logs with stacktraces
([gist](https://gist.github.com/gbamparop/0da21ca7f65b24c4a9c071ce9e9b97b0)).
Please note that these are test data and some fields that are not used
by stacktraces might not be consistent
2. View relevant logs in Discover (Query: `service.name: "synth-node-0"
OR apache_tomcat :*`, Time range: Jan 1, 2025 - now)

---------

Co-authored-by: kibanamachine <[email protected]>
(cherry picked from commit 368475e)

# Conflicts:
#	.github/CODEOWNERS
#	x-pack/platform/packages/shared/kbn-event-stacktrace/src/components/stacktrace/cause_stacktrace.tsx
#	x-pack/platform/packages/shared/kbn-event-stacktrace/src/components/stacktrace/frame_heading.tsx
#	x-pack/platform/packages/shared/kbn-event-stacktrace/src/components/stacktrace/library_stacktrace.tsx
#	x-pack/platform/packages/shared/kbn-event-stacktrace/src/components/stacktrace/stackframe.tsx
#	x-pack/platform/packages/shared/kbn-event-stacktrace/src/components/stacktrace/variables.tsx
#	x-pack/platform/packages/shared/kbn-key-value-metadata-table/src/formatted_value.tsx
#	x-pack/solutions/observability/plugins/apm/tsconfig.json
@gbamparop
Copy link
Contributor Author

improve cells rendering but I guess it's tricky as stacktrace data is split in multiple fields, right?

I really like this idea too, and I think we could do it even if the data is split across fields. We have access to the full record when rendering a cell value, so we could use those other fields when rendering error.stack_trace for a complex view, and fall back to something simpler when some are missing or only error.stack_trace is available.

@davismcphee created a placeholder issue #208168

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jan 24, 2025
@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

1 similar comment
@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

gbamparop added a commit that referenced this pull request Jan 28, 2025
…4521) (#208115)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[One Discover] Display stacktrace in the logs overview tab
(#204521)](#204521)

<!--- Backport version: 9.6.4 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Giorgos
Bamparopoulos","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-01-22T16:06:14Z","message":"[One
Discover] Display stacktrace in the logs overview tab (#204521)\n\n## 📓
Summary\r\nAdds a new section to the overview tab in the log details
flyout in\r\nDiscover to display stacktrace information for logs and
exceptions.\r\n\r\nIn a follow-up, the stacktrace could be moved to a
new tab in the log\r\ndetails flyout and actions can be added to the
stacktrace (and quality)\r\nicons in the document table to open the
relevant sections in the flyout.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/190460\r\n\r\n### APM - Log
stacktrace (library frames)\r\n<img width=\"1470\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8991f882-d329-4bc5-aa37-424576bcee72\"\r\n/>\r\n\r\n###
APM - Exception (with cause)\r\n<img width=\"1476\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cfbf24a7-6f82-48f1-b275-5aac977411ac\"\r\n/>\r\n\r\n###
APM - Exception (simple stacktrace)\r\n<img width=\"1474\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/fc0306c4-5fcd-4b74-bb0d-c1784a48d677\"\r\n/>\r\n\r\n###
Apache Tomcat Integration (Catalina) - Stacktrace\r\n<img width=\"1472\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/281f1822-faea-4e2d-9515-c11a9ee12f50\"\r\n/>\r\n\r\n##
📝 Notes for reviewers\r\n- The `@kbn/apm-types` package was marked as
platform / shared as it's\r\nbeing used by
the\r\n[unified_doc_viewer](https://github.com/elastic/kibana/blob/main/src/plugins/unified_doc_viewer/kibana.jsonc)\r\n-
The code used to render stacktraces in APM was moved into a
new\r\n`@kbn/event-stacktrace` package as it is reused in
the\r\n`unified_doc_viewer`\r\n- The code used to render metadata table
in APM was moved into a new\r\n`@kbn/key-value-metadata-table`
package\r\n\r\n## 🧪 Testing instructions\r\nThe deployed environments
have sample logs that can be used (time range:\r\nJan 1, 2025 - now).
For a local setup, please follow the instructions\r\nbelow:\r\n\r\n1.
Ingest sample logs with
stacktraces\r\n([gist](https://gist.github.com/gbamparop/0da21ca7f65b24c4a9c071ce9e9b97b0)).\r\nPlease
note that these are test data and some fields that are not used\r\nby
stacktraces might not be consistent\r\n2. View relevant logs in Discover
(Query: `service.name: \"synth-node-0\"\r\nOR apache_tomcat :*`, Time
range: Jan 1, 2025 - now)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"368475e8e55845e17fd4621c1ae60ba1e983bb8f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v8.18.0"],"title":"[One
Discover] Display stacktrace in the logs overview
tab","number":204521,"url":"https://github.com/elastic/kibana/pull/204521","mergeCommit":{"message":"[One
Discover] Display stacktrace in the logs overview tab (#204521)\n\n## 📓
Summary\r\nAdds a new section to the overview tab in the log details
flyout in\r\nDiscover to display stacktrace information for logs and
exceptions.\r\n\r\nIn a follow-up, the stacktrace could be moved to a
new tab in the log\r\ndetails flyout and actions can be added to the
stacktrace (and quality)\r\nicons in the document table to open the
relevant sections in the flyout.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/190460\r\n\r\n### APM - Log
stacktrace (library frames)\r\n<img width=\"1470\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8991f882-d329-4bc5-aa37-424576bcee72\"\r\n/>\r\n\r\n###
APM - Exception (with cause)\r\n<img width=\"1476\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cfbf24a7-6f82-48f1-b275-5aac977411ac\"\r\n/>\r\n\r\n###
APM - Exception (simple stacktrace)\r\n<img width=\"1474\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/fc0306c4-5fcd-4b74-bb0d-c1784a48d677\"\r\n/>\r\n\r\n###
Apache Tomcat Integration (Catalina) - Stacktrace\r\n<img width=\"1472\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/281f1822-faea-4e2d-9515-c11a9ee12f50\"\r\n/>\r\n\r\n##
📝 Notes for reviewers\r\n- The `@kbn/apm-types` package was marked as
platform / shared as it's\r\nbeing used by
the\r\n[unified_doc_viewer](https://github.com/elastic/kibana/blob/main/src/plugins/unified_doc_viewer/kibana.jsonc)\r\n-
The code used to render stacktraces in APM was moved into a
new\r\n`@kbn/event-stacktrace` package as it is reused in
the\r\n`unified_doc_viewer`\r\n- The code used to render metadata table
in APM was moved into a new\r\n`@kbn/key-value-metadata-table`
package\r\n\r\n## 🧪 Testing instructions\r\nThe deployed environments
have sample logs that can be used (time range:\r\nJan 1, 2025 - now).
For a local setup, please follow the instructions\r\nbelow:\r\n\r\n1.
Ingest sample logs with
stacktraces\r\n([gist](https://gist.github.com/gbamparop/0da21ca7f65b24c4a9c071ce9e9b97b0)).\r\nPlease
note that these are test data and some fields that are not used\r\nby
stacktraces might not be consistent\r\n2. View relevant logs in Discover
(Query: `service.name: \"synth-node-0\"\r\nOR apache_tomcat :*`, Time
range: Jan 1, 2025 - now)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"368475e8e55845e17fd4621c1ae60ba1e983bb8f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204521","number":204521,"mergeCommit":{"message":"[One
Discover] Display stacktrace in the logs overview tab (#204521)\n\n## 📓
Summary\r\nAdds a new section to the overview tab in the log details
flyout in\r\nDiscover to display stacktrace information for logs and
exceptions.\r\n\r\nIn a follow-up, the stacktrace could be moved to a
new tab in the log\r\ndetails flyout and actions can be added to the
stacktrace (and quality)\r\nicons in the document table to open the
relevant sections in the flyout.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/190460\r\n\r\n### APM - Log
stacktrace (library frames)\r\n<img width=\"1470\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8991f882-d329-4bc5-aa37-424576bcee72\"\r\n/>\r\n\r\n###
APM - Exception (with cause)\r\n<img width=\"1476\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cfbf24a7-6f82-48f1-b275-5aac977411ac\"\r\n/>\r\n\r\n###
APM - Exception (simple stacktrace)\r\n<img width=\"1474\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/fc0306c4-5fcd-4b74-bb0d-c1784a48d677\"\r\n/>\r\n\r\n###
Apache Tomcat Integration (Catalina) - Stacktrace\r\n<img width=\"1472\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/281f1822-faea-4e2d-9515-c11a9ee12f50\"\r\n/>\r\n\r\n##
📝 Notes for reviewers\r\n- The `@kbn/apm-types` package was marked as
platform / shared as it's\r\nbeing used by
the\r\n[unified_doc_viewer](https://github.com/elastic/kibana/blob/main/src/plugins/unified_doc_viewer/kibana.jsonc)\r\n-
The code used to render stacktraces in APM was moved into a
new\r\n`@kbn/event-stacktrace` package as it is reused in
the\r\n`unified_doc_viewer`\r\n- The code used to render metadata table
in APM was moved into a new\r\n`@kbn/key-value-metadata-table`
package\r\n\r\n## 🧪 Testing instructions\r\nThe deployed environments
have sample logs that can be used (time range:\r\nJan 1, 2025 - now).
For a local setup, please follow the instructions\r\nbelow:\r\n\r\n1.
Ingest sample logs with
stacktraces\r\n([gist](https://gist.github.com/gbamparop/0da21ca7f65b24c4a9c071ce9e9b97b0)).\r\nPlease
note that these are test data and some fields that are not used\r\nby
stacktraces might not be consistent\r\n2. View relevant logs in Discover
(Query: `service.name: \"synth-node-0\"\r\nOR apache_tomcat :*`, Time
range: Jan 1, 2025 - now)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"368475e8e55845e17fd4621c1ae60ba1e983bb8f"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:version Backport to applied version labels ci:project-deploy-observability Create an Observability project release_note:enhancement Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team v8.18.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[One Discover] Display stacktraces in the log details flyout
9 participants