elastic/kibana

[APM] Annotations: Service version label could be better

Open

#66,138 建立於 2020年5月11日

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

描述

I'm not really sure what to call this issue. I've been playing around with the annotations API, and I'm wondering if we should reconsider the "Service version" graph label and "Version" key in the popup:

When annotations are derived from a change in service.version, this makes sense, but with custom labels on annotations, it might make more sense to remove the "Version" key, and change the "Service version" label to something else.

貢獻者指南

技術棧
typescriptreact
領域
frontendobservability
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
familiarity with APM annotationsbasic knowledge of Kibana UI components
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Look for the APM annotations component in the Kibana codebase. The issue references the 'Service version' label and 'Version' key in the popup. Locate the relevant file, likely in the APM plugin under x pack/plugins/apm, and modify the string. Ensure the change aligns with the desired behavior described in the issue. The discussion in the comments may provide additional context.