# Possible to redirect Data Visualizer to existing ingest pipeline for import? **URL:** \ **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:** 1\ **Showing post:** 2
**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")
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. --- _[View the full topic](https://discuss.elastic.co/t/possible-to-redirect-data-visualizer-to-existing-ingest-pipeline-for-import/306063)._