Skip to content

Commit 300fec7

Browse files
committed
Added tips
1 parent 3649496 commit 300fec7

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

manage-data/ingest/transform-enrich/error-handling.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,12 @@ Ingest pipelines in Elasticsearch are powerful tools for transforming and enrich
1414

1515
Errors in ingest pipelines typically fall into the following categories:
1616

17-
* Parsing Errors: Occur when a processor fails to parse a field, such as a date or number.
18-
* Missing Fields: Happen when a required field is absent in the document.
17+
- Parsing Errors: Occur when a processor fails to parse a field, such as a date or number.
18+
- Missing Fields: Happen when a required field is absent in the document.
1919

20-
**Recommendation**: Create an `error-handling-pipeline` that sets `event.kind` to `pipeline_error` and stores the error message, along with the tag from the failed processor, in the `error.message` field. Including a tag is especially helpful when using multiple `grok`, `dissect`, or `script` processors, as it helps identify which one caused the failure.
20+
:::tip
21+
Create an `error-handling-pipeline` that sets `event.kind` to `pipeline_error` and stores the error message, along with the tag from the failed processor, in the `error.message` field. Including a tag is especially helpful when using multiple `grok`, `dissect`, or `script` processors, as it helps identify which one caused the failure.
22+
:::
2123

2224
The `on_failure` parameter can be defined either for individual processors or at the pipeline level to catch exceptions that may occur during document processing. The `ignore_failure` option allows a specific processor to silently skip errors without affecting the rest of the pipeline.
2325

0 commit comments

Comments
 (0)