kibana/x-pack/plugins/ingest_pipelines
Alejandro Fernández Haro fd09c26d15
async-import plugins in the server side (#170856)
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-11-15 00:55:56 -07:00
..
__jest__/client_integration Upgrade EUI to v90.0.0 (#170179) 2023-11-03 10:19:31 -07:00
common Add _meta field to Ingest pipelines form (#149976) 2023-02-09 15:39:19 +00:00
public [ES UI Shared] Remove old ace based EuiCodeEditor (#169613) 2023-10-25 21:14:43 +02:00
server async-import plugins in the server side (#170856) 2023-11-15 00:55:56 -07:00
jest.config.js [jest] update config files to get coverage per plugin (#111299) 2021-09-09 08:14:56 +02:00
kibana.jsonc [Ingest Pipelines] Add license checks for processors (#154525) 2023-04-12 14:28:51 +02:00
README.md Updates Github link references from master to main (#116789) 2021-10-29 09:53:08 -07:00
tsconfig.json [KibanaReact] Use settings service in useUiSetting hook (#154710) 2023-05-12 10:47:56 +03:00

Ingest Pipelines UI

Summary

The ingest_pipelines plugin provides Kibana support for Elasticsearch's ingest pipelines.

This plugin allows Kibana to create, edit, clone and delete ingest pipelines. It also provides support to simulate a pipeline.

It requires a Basic license and the following cluster privileges: manage_pipeline and cluster:monitor/nodes/info.


Development

A new app called Ingest Pipelines is registered in the Management section and follows a typical CRUD UI pattern. The client-side portion of this app lives in public/application and uses endpoints registered in server/routes/api. For more information on the pipeline processors editor component, check out the component readme.

See the kibana contributing guide for instructions on setting up your development environment.

Test coverage

The app has the following test coverage:

  • API integration tests
  • Smoke-level functional test
  • Client-integration tests

Quick steps for manual testing

You can run the following request in Console to create an ingest pipeline:

PUT _ingest/pipeline/test_pipeline
{
   "description": "_description",
    "processors": [
      {
        "set": {
          "field": "field1",
          "value": "value1"
        }
      },
      {
        "rename": {
          "field": "dont_exist",
          "target_field": "field1",
          "ignore_failure": true
        }
      },
      {
        "rename": {
          "field": "foofield",
          "target_field": "new_field",
          "on_failure": [
            {
              "set": {
                "field": "field2",
                "value": "value2"
              }
            }
          ]
        }
      },
      {
        "drop": {
          "if": "false"
        }
      },
      {
        "drop": {
          "if": "true"
        }
      }
    ]
}

Then, go to the Ingest Pipelines UI to edit, delete, clone, or view details of the pipeline.

To simulate a pipeline, go to the "Edit" page of your pipeline. Click the "Add documents" link under the "Processors" section. You may add the following sample documents to test the pipeline:

// The first document in this example should trigger the on_failure processor in the pipeline, while the second one should succeed.
[
  {
    "_index": "my_index",
    "_id": "id1",
    "_source": {
      "foo": "bar"
    }
  },
  {
    "_index": "my_index",
    "_id": "id2",
    "_source": {
      "foo": "baz",
      "foofield": "bar"
    }
  }
]

Alternatively, you can add a document from an existing index, or create some sample data of your own. Afterward, click the "Run the pipeline" button to view the output.