elastic/kibana

[APM] Service icons metadata endpoint doesn't apply environment filter

Open

#175,662 创建于 2024年1月26日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)TypeScript (19,065 star) (8,021 fork)batch import
Team:obs-ux-infra_services - DEPRECATEDbuggood first issue

描述

We didn't consider the case where each environment could use different cloud provider or platform.

https://github.com/elastic/kibana/blob/beff74e19e94c7d3c609a2be0cb1d4b2f28da043/x-pack/plugins/apm/server/routes/services/route.ts#L282-L311

贡献者指南

技术栈
typescriptnodejsrest api
领域
backendapiobservability
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
basic understanding of Elastic APMfamiliarity with Node.js/TypeScriptknowledge of environment filtering
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
The issue is in x pack/plugins/apm/server/routes/services/route.ts, specifically around lines 282-311, where the service icons metadata endpoint does not apply the environment filter. Investigate how other endpoints in the same file or other APM routes implement environment filtering. Look at the request handler and the service logic to determine where the filter should be added. Check if there are existing tests for this endpoint to understand expected behavior.