# Possible to redirect Data Visualizer to existing ingest pipeline for import?

**URL:** <https://discuss.elastic.co/t/possible-to-redirect-data-visualizer-to-existing-ingest-pipeline-for-import/306063>\
**Category:** Elasticsearch\
**Created:** [May 31, 2022, 7:46pm UTC](https://discuss.elastic.co/t/possible-to-redirect-data-visualizer-to-existing-ingest-pipeline-for-import/306063 "2022-05-31T19:46:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fl33t](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fl33t/32/106401_2.png) [@fl33t](https://discuss.elastic.co/u/fl33t)\
**Post date:** [May 31, 2022, 7:46pm UTC](https://discuss.elastic.co/t/possible-to-redirect-data-visualizer-to-existing-ingest-pipeline-for-import/306063/1 "2022-05-31T19:46:56Z")

</div>

In the ML section, if we know the type of log file that we want to upload for visualization and analysis, would it be possible to redirect it to an existing ingest pipeline (with associated mappings and index settings) instead of having the ML guess?

Such as "winlogbeat-[version]-security" for example.

Manually modifying these settings in the Advanced section for every file during import is simply not feasible.

Cheers!

---

<div class="post-metadata">

**Author:** ![fl33t](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fl33t/32/106401_2.png) [@fl33t](https://discuss.elastic.co/u/fl33t)\
**Post date:** [June 10, 2022, 7:51pm UTC](https://discuss.elastic.co/t/possible-to-redirect-data-visualizer-to-existing-ingest-pipeline-for-import/306063/2 "2022-06-10T19:51:41Z")

</div>

I believe that I will be closing this thread since I'm not sure that this is quite what the ML section is for.

The original purpose was to upload logs that had been manually gathered on an offline server.

Although the solution is not perfect as I still haven't found a way to have the data parsed through winlogbeat pipelines, I did manage to send large series of ndjson data through **filebeat** , which I consider the (partial) solution for the time being.

I'm also exploring ways to achieve this via logstash in [this](https://discuss.elastic.co/t/manually-upload-winlogbeat-ndjson-files-to-elasticsearch/306046/6) thread, in case anyone's interested.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 8, 2022, 7:52pm UTC](https://discuss.elastic.co/t/possible-to-redirect-data-visualizer-to-existing-ingest-pipeline-for-import/306063/3 "2022-07-08T19:52:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.