# Path files Visualizations

**URL:** <https://discuss.elastic.co/t/path-files-visualizations/323899>\
**Category:** Kibana\
**Created:** [January 25, 2023, 9:26am UTC](https://discuss.elastic.co/t/path-files-visualizations/323899 "2023-01-25T09:26:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![m3bgwad](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@m3bgwad](https://discuss.elastic.co/u/m3bgwad)\
**Post date:** [January 25, 2023, 9:26am UTC](https://discuss.elastic.co/t/path-files-visualizations/323899/1 "2023-01-25T09:26:07Z")

</div>

Hello everyone,  
I Hobe ta all is very well,  
I have a Q regarding use path files to visualize them in Kibana.  
Is it possible to find a way to use Kibana search engine to find specific line in the set of files without store this files in ES DB?

Thank you for advance,

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [January 25, 2023, 9:41am UTC](https://discuss.elastic.co/t/path-files-visualizations/323899/2 "2023-01-25T09:41:19Z")

</div>

Hi Mohamed,

Your data would need to be stored in Elasticsearch to be visualised in Kibana. Where is your data at the moment? We do have various connectors and approaches to help with ingest from other sources that could help you.

---

<div class="post-metadata">

**Author:** ![m3bgwad](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@m3bgwad](https://discuss.elastic.co/u/m3bgwad)\
**Post date:** [January 25, 2023, 10:47am UTC](https://discuss.elastic.co/t/path-files-visualizations/323899/3 "2023-01-25T10:47:41Z")

</div>

@carly.richmond Thank you for your response,

> [@carly.richmond](#):
>
> Your data would need to be stored in Elasticsearch to be visualised in Kibana.

I am aware that ES stored data in `/var/lib/elasticsearch` but I have some different data stored in different files I need to visualize these files. is there wayes to support this?

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [January 25, 2023, 12:45pm UTC](https://discuss.elastic.co/t/path-files-visualizations/323899/4 "2023-01-25T12:45:31Z")

</div>

You'll need to ingest the files into Elasticsearch and make available via a data view on top of the index.

Can you give details on the files as to whether they are regularly generated files such as logs or a one off file for analysis? You have a few options for file ingest such as [one off via the file ingestion](https://www.elastic.co/guide/en/kibana/current/connect-to-elasticsearch.html#upload-data-kibana), Logstash or integrations.

---

<div class="post-metadata">

**Author:** ![m3bgwad](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@m3bgwad](https://discuss.elastic.co/u/m3bgwad)\
**Post date:** [January 25, 2023, 12:58pm UTC](https://discuss.elastic.co/t/path-files-visualizations/323899/5 "2023-01-25T12:58:03Z")

</div>

what will happen if I use pata.path to NFS mounted path, please look at this page specifically ` but this means that it will work correctly on properly-configured remote block devices (e.g. a SAN) and remote filesystems (e.g. NFS) as long as the remote storage behaves no differently from local storage`

> **[Node | Elasticsearch Guide \[8.2\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.2/modules-node.html#data-path)**

---

<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:** [February 22, 2023, 12:59pm UTC](https://discuss.elastic.co/t/path-files-visualizations/323899/6 "2023-02-22T12:59:00Z")

</div>

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