# Displaying the application log data in Kibana - Log file content field is missing in Elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [December 20, 2021, 10:48am UTC](https://discuss.elastic.co/t/displaying-the-application-log-data-in-kibana-log-file-content-field-is-missing-in-elasticsearch/292448 "2021-12-20T10:48:59Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![online](https://avatars.discourse-cdn.com/v4/letter/o/bb73d2/32.png) [@online](https://discuss.elastic.co/u/online)\ **Post date:** [December 20, 2021, 10:48am UTC](https://discuss.elastic.co/t/displaying-the-application-log-data-in-kibana-log-file-content-field-is-missing-in-elasticsearch/292448/1 "2021-12-20T10:48:59Z")
Hello Friends, I am trying to setup an Elasticsearch index to display log contents from an application using Kibana. I setup the Filebeat on my application server and it created an index with 25 fields in Elasticsearch. Please note the application log is not any of the default log types available via the Filebeat. Data flow is like this: Filebeat\>\> Elasticsearch \>\> Kibana. Problem I am having is the contents of the log files are not being included in the Elasticsearch index it created, as a field for me to display via Kibana. It has the field "count of records" and it shows different numbers for each of the log files. So I am assuming the Elasticsearch Index is aware of what is inside, each of the log files in terms of number of rows, but haven't created a field for it for some reason. It is somewhat similar to the below issue, but not exactly the same. > [@Parse the logs with FileBeat-ElasticSearch and Display on Kibana](https://discuss.elastic.co/t/parse-the-logs-with-filebeat-elasticsearch-and-display-on-kibana/107802): > > I'm very new to the forums of Elastic. I have gone through these tools and few videos some hours ago and setup Kibana, Logstash and Elasticsearch on my local windows machine (on a private network). I managed to parse the lines from command line. Setup used was ==\> logstash --\> elastic search --\> Kibana. I need some help to Parse the logs with FileBeat and elastic search then display on Kibana with different filters and statistics. Currently, I don't want to parse using logstash. Simply, want… Thank you for your answers. Cheers. ---
**Author:** ![online](https://avatars.discourse-cdn.com/v4/letter/o/bb73d2/32.png) [@online](https://discuss.elastic.co/u/online)\ **Post date:** [December 22, 2021, 2:58am UTC](https://discuss.elastic.co/t/displaying-the-application-log-data-in-kibana-log-file-content-field-is-missing-in-elasticsearch/292448/2 "2021-12-22T02:58:50Z")
Hello, I tried to edit the original post instead of replying to it. Couple of things have changed. It seems if I use the "Discover" option in ELK and look for the index and it's fields, the field with the message details appear there.. As originally posted, this isn't the case when trying to create Visualization using the same index, where this field called "message" is invisible. The second thing I want to ask is the following. I have the log file with two prominent fields as below. `####2021-12-21 11:10:10,820 ThreadId:99 INFO irpuyc_Impl - -> Request() <[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel'> ####2021-12-21 11:10:13,830 ThreadId:99 ERROR subsystem.api.subSystemFuture - error took place <[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'>` Based on thread id which is Thread:99 in this case, the ERROR and INFO lines are related via Thread:99. The number 99 keeps changing. Is there a way for me to find all the related INFO lines based on TreadId, if the filebeat finds an ERROR line in the logs? Thank you for any feedback on this. Much appreciated. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 19, 2022, 2:59am UTC](https://discuss.elastic.co/t/displaying-the-application-log-data-in-kibana-log-file-content-field-is-missing-in-elasticsearch/292448/3 "2022-01-19T02:59:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.