elastic/kibana

Mobile filters does not filter out non-crash errors in error details

Open

#172,976 建立於 2023年12月8日

在 GitHub 查看
 (8 留言) (0 反應) (0 負責人)TypeScript (19,065 star) (8,021 fork)batch import
Team:obs-ux-infra_services - DEPRECATEDapm:mobilebuggood first issue

描述

Kibana version: edge-lite

Describe the bug: On the Mobile Errors & Crashes crashes tab, in the dropdown filters you can see devices/os versions/app versions/network connection types that are from non-crash errors. In the screenshot we can see both iPhone12,5 and arm64 showing in the drop down, but only iPhone12,5 showing up in the most affected chart, as well as only 1 occurrence existing for crashes.

Expected behavior: Only filter options from error.type: crash errors should show in these dropdowns

Screenshots (if relevant):

貢獻者指南

技術棧
typescriptreact
領域
frontendanalyticssearch
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Knowledge of Kibana's APM pluginFamiliarity with React
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the mobile errors and crashes tab filter logic to understand why non crash error types appear. Look at the UI components in the APM plugin, likely under x pack/plugins/observability solution/apm/public/components/app/mobile/errors and crashes. Check how filter options are generated and ensure they apply a filter for error.type: crash.