ingest-pipelines

Name: ingest-pipelines
Availability: InStock
Author: elastic

Design and enforce Elasticsearch ingest pipelines with branching and on_failure handling.

15|5|Updated May 11, 2026

Search Tags:#branching #ecs #error-handling #pipelines #ingest #elastic

Ready to run

npx skills add https://github.com/elastic/integration-skills --skill ingest-pipelines

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ingest-pipelines
Source: https://github.com/elastic/integration-skills/tree/main/skills/ingest-pipelines
Command: npx skills add https://github.com/elastic/integration-skills --skill ingest-pipelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides authoritative guidance for designing, validating, and maintaining Elasticsearch ingest pipelines, including single-path parsing, branching patterns, on_failure strategies, and CEL vs non-CEL data handling.

Core Features & Use Cases

Authoritative patterns for building and maintaining ingest pipelines in Elastic integrations, covering parsing, enrichment, and ECS mapping.
Supports single-path pipelines as well as branching with sub-pipelines, comprehensive on_failure handling, and test fixtures.
Use case: when constructing a new data stream or updating an existing integration, follow the standardized workflow to ensure consistent behavior and observability.

Quick Start

Create a ready-to-apply ingest_pipeline design plan for a new data stream, including default.yml routing and on_failure blocks.

Frequently Asked Questions about ingest-pipelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design an Elasticsearch ingest pipeline with branching and sub-pipelines?▼

Elasticsearch ingest pipelines can use branching to route documents through sub-pipelines. This Skill provides authoritative patterns for single-path parsing and branching, ensuring consistent ECS mapping and auditable pipeline design across data streams.

What is the best way to handle on_failure errors in Elasticsearch ingest pipelines?▼

Handling on_failure errors in Elasticsearch ingest pipelines requires robust fallback strategies. This Skill enforces standard error-handling patterns, including on_failure blocks for both CEL and non-CEL contexts, to prevent data loss and ensure observability during parsing failures.

How do I map data to ECS fields when building a new Elastic integration data stream?▼

Mapping data to ECS fields when building Elastic integrations requires standardized ingest pipeline patterns. This Skill enforces authoritative rules for parsing and ECS mapping, providing a ready-to-apply design plan including default.yml routing to ensure consistent behavior.

Does this ingest pipeline guidance apply to both CEL and non-CEL data processing contexts?▼

Yes, this ingest pipeline guidance applies to both CEL and non-CEL data processing contexts. It enforces standard rules and references processor-cookbook patterns alongside specific CEL patterns to ensure consistent, auditable pipeline design across different data handling methods.

When do I need to use sub-pipelines instead of a single-path ingest pipeline in Elasticsearch?▼

Sub-pipelines are needed when your Elasticsearch ingest pipeline requires branching to handle diverse document structures. This Skill provides guidelines for both single-path parsing and branching with sub-pipelines, allowing you to route data streams dynamically while maintaining consistent ECS mapping.