elastic/kibana

[APM] Fix diagnostics page

Open

#177581 opened on Feb 22, 2024

View on GitHub
 (4 comments) (0 reactions) (0 assignees)TypeScript (19,065 stars) (8,021 forks)batch import
Team:obs-ux-infra_services - DEPRECATEDbuggood first issueinfo-needed

Description

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}"

Contributor guide

Tech stack
typescriptnodejsreact
Domain
frontendbackendobservability
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptKibana development setupUnderstanding of ingest pipelines
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
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.