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.