elastic/kibana

[APM] Fix diagnostics page

Open

#177,581 建立於 2024年2月22日

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

描述

On the APM Diagnostics page, we use the processors.grok to filter the ingest pipelines here.

On 8.14 this PR was merged removing these processors https://github.com/elastic/integrations/pull/9185/files#diff-35903ffd0e4793a494fe0ce95c930b38b9eda7b6bdbfe8e8cf16dc34f9841958L9. We need to update the filter_path and the code that checks if a ingest pipeline is valid.

Without this, we'll always display a warning message on the page:

The expected processor for "observer.version" was not found in "${ingestPipeline.id}"

貢獻者指南

技術棧
typescriptnodejsreact
領域
frontendbackendobservability
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TypeScriptKibana development setupUnderstanding of ingest pipelines
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Review the linked file at x pack/plugins/apm/server/routes/diagnostics/bundle/get indices.ts, specifically the filter path usage. Also examine the linked PR at elastic/integrations#9185 which removes processors.grok. Update the filter path to reflect the removal and adjust the validation code accordingly. Ensure the warning message no longer appears incorrectly.