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.