opensearch-project/OpenSearch

[Feature Request] Add granular logging for ingest pipeline processor failure

Open

#12,553 opened on Mar 7, 2024

View on GitHub
 (11 comments) (0 reactions) (1 assignee)Java (1,505 forks)batch import
enhancementgood first issueingest-pipeline

Repository metrics

Stars
 (8,123 stars)
PR merge metrics
 (Avg merge 5d 9h) (266 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe

Currently, within the OpenSearch project, the logging mechanism for failures in the ingest pipeline processors lacks granularity, we only have failure metric count. As a result, troubleshooting and debugging issues related to failed processors become cumbersome and inefficient for developers and administrators.

https://github.com/opensearch-project/OpenSearch/blob/3056b67fb0037df9045bbdd0b828929b2e17aaed/server/src/main/java/org/opensearch/ingest/CompoundProcessor.java#L164-L186

Describe the solution you'd like

We propose adding a debug level logging feature dedicated to capturing detailed information about failures occurring within ingest pipeline processors.

Related component

Indexing

Contributor guide

Research direction
Examine the CompoundProcessor class and implement debug level logging for processor failures.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75