# Elasticsearch and its files? **URL:** \ **Category:** Elasticsearch\ **Created:** [September 26, 2016, 8:28am UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492 "2016-09-26T08:28:42Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![dop87](https://avatars.discourse-cdn.com/v4/letter/d/a5b964/32.png) [@dop87](https://discuss.elastic.co/u/dop87)\ **Post date:** [September 26, 2016, 8:28am UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492/1 "2016-09-26T08:28:42Z")
Hi everyone. Im kinda brand new to elasticsearch . Is there a way to see what files that are going through elasticsearch? Lets say my elasticsearch are running some files that are passing through. Is there a way to see what file there are passing through and how long that file will take? maybe a plugin or something ? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [September 26, 2016, 10:12am UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492/2 "2016-09-26T10:12:21Z")
Not sure I understand the question. What do you mean by "files going through elasticsearch"? Are you talking about the files elasticsearch is storing locally on the hard drive? ---
**Author:** ![dop87](https://avatars.discourse-cdn.com/v4/letter/d/a5b964/32.png) [@dop87](https://discuss.elastic.co/u/dop87)\ **Post date:** [September 26, 2016, 10:22am UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492/3 "2016-09-26T10:22:46Z")
So right now im using a program that i setup to run with elasticsearch engine. now it could be really nice if there was a way to see what elasticsearch was doing, and what is going through the engine. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [September 26, 2016, 10:58am UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492/4 "2016-09-26T10:58:54Z")
From a JSON document to the bits on disk? Is that what you are looking for? Like: - parse JSON - analyze text - build the inverted index - write on disk Well I don't think such a picture exists as it's really complex and depends on many factors. But again may be I don't understand your question. Why are you asking that actually? ---
**Author:** ![Jaishil\_Dhal](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@Jaishil\_Dhal](https://discuss.elastic.co/u/Jaishil_Dhal)\ **Post date:** [September 26, 2016, 11:31am UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492/5 "2016-09-26T11:31:17Z")
go throw this docs it ll help u.. [https://www.elastic.co/guide/en/kibana/current/getting-started.html](https://www.elastic.co/guide/en/kibana/current/getting-started.html) ---
**Author:** ![dop87](https://avatars.discourse-cdn.com/v4/letter/d/a5b964/32.png) [@dop87](https://discuss.elastic.co/u/dop87)\ **Post date:** [September 27, 2016, 6:41am UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492/6 "2016-09-27T06:41:38Z")
hI i Just want to see what the engine is doing, what files are passing through and so. if its possible to see what it is working on. ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [September 27, 2016, 12:15pm UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492/7 "2016-09-27T12:15:54Z")
Elasticsearch is a distributed system. You can use monitoring tools like kopf, head, marvel etc. to gain insight. Monitoring a single query through the system can be achieved by using the query profiler [https://www.elastic.co/elasticon/conf/2016/sf/profiling-elasticsearch-queries-for-fun-and-profit](https://www.elastic.co/elasticon/conf/2016/sf/profiling-elasticsearch-queries-for-fun-and-profit) Monitoring indexing is possible by evaluating the Java API `BulkResponse` object which Elasticsearch returns. Index segment monitoring can be done by plugins like Whatson [https://github.com/xyu/elasticsearch-whatson](https://github.com/xyu/elasticsearch-whatson) Low-level monitoring (files etc.) is hard because of several reasons: the volume of data is massive, the monitored nodes are distributed and working asynchronously, and most important the insight will be rather limited by watching raw data and events. That is the reason why monitoring tools like Marvel do the heavy lifting and show graphical data (trends) and statistics. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:16pm UTC](https://discuss.elastic.co/t/elasticsearch-and-its-files/61492/8 "2017-07-05T22:16:57Z")