You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A section was added to the overview tab in the log details flyout in Discover as part of #204521 to display stacktrace information for logs and exceptions. It covers stacktraces for APM errors with the same components used in the error details page in the APM app as well as formatted stacktraces ingested to the error.stack_trace ECS field.
Building on top of this work, a cell renderer can be created to display formatted stacktraces in the document table.
🎨 Design
TBD
✔️ Acceptance Criteria
TBD
❓ Open questions
The APM stacktraces within error.log and error.exception fields, can consist of multiple stack frames in a stacktrace array. Does it make sense to use more than one field in the cell renderer? (See comment)
📓 Summary
A section was added to the overview tab in the log details flyout in Discover as part of #204521 to display stacktrace information for logs and exceptions. It covers stacktraces for APM errors with the same components used in the error details page in the APM app as well as formatted stacktraces ingested to the error.stack_trace ECS field.
Building on top of this work, a cell renderer can be created to display formatted stacktraces in the document table.
🎨 Design
TBD
✔️ Acceptance Criteria
TBD
❓ Open questions
error.log
anderror.exception
fields, can consist of multiple stack frames in astacktrace
array. Does it make sense to use more than one field in the cell renderer? (See comment)🔗 Links
The text was updated successfully, but these errors were encountered: