# Data not visibile in Kibana
**URL:** https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122
**Category:** Elasticsearch
**Created:** [December 29, 2021, 1:31pm UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122 "2021-12-29T13:31:10Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@d6036de2b54af16665f4](https://discuss.elastic.co/u/d6036de2b54af16665f4)
#### Post date: [December 29, 2021, 1:31pm UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/1 "2021-12-29T13:31:10Z")
Hello,
I ingested data from s3 bucket into Elasticsearch through Logstash pipelines.
BUT I AM NOT ABLE TO visualize DATA IN KIBANA .
I am only able to see data till october monthsm and after that no data is visible there....
Any suggestion would be helpufull....
---
### Author:  [@Petr.Simik](https://discuss.elastic.co/u/Petr.Simik)
#### Post date: [December 31, 2021, 10:46am UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/2 "2021-12-31T10:46:38Z")
> [@d6036de2b54af16665f4](#):
>
> able to see data till october monthsm and after that no data is visible th
Try to query the data from dev\_tool
GET indexname/\_search
and check the timestamp which is used by kibana index pattern
its value might be in incorrect format
---
### Author:  [@d6036de2b54af16665f4](https://discuss.elastic.co/u/d6036de2b54af16665f4)
#### Post date: [December 31, 2021, 1:14pm UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/3 "2021-12-31T13:14:50Z")
okay I will check that once and will let you know....
But,
Elasticsearch is their on the same machine...
And also when I am running Logstash Logs I am getting ...
1. [2021-12-24T06:25:16,758][ERROR][org.logstash.Logstash] java.lang.OutOfMemoryError: Java heap space
[2021-12-24T05:12:31,352][ERROR][logstash.outputs.Elasticsearch] Attempted to send a bulk request to Elasticsearch' but Elasticsearch appears to be unreachable or down! {:error\_message=\>"Elasticsearch Unreachable: [[http://XXXXXXXXXXxXXXX.XX-XXXXXXXXX.amazonaws.com:9200/](http://xxxxxxxxxxxxxxx.xx-xxxxxxxxx.amazonaws.com:9200/)][Manticore::ClientProtocolException] [XXXXXXXXXXXXXXXXXXXXXXXXXXXXX.ZZZZZZZZZZZ.amazonaws.com:9200](http://xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.zzzzzzzzzzz.amazonaws.com:9200/) failed to respond", :class=\>"LogStash::Outputs::Elasticsearch::HttpClient::Pool::HostUnreachableError", :will\_retry\_in\_seconds=\>2}
[2021-12-24T03:54:42,052][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit
[2021-12-24T03:35:26,776][ERROR][logstash.licensechecker.licensereader] Unable to retrieve license information from license server {:message=\>"Elasticsearch Unreachable: [[http://XXXXXXXX.XXXXXX.XXXXXXXXnaws.com:9200/](http://xxxxxxxx.xxxxxx.xxxxxxxxnaws.com:9200/)][Manticore::ClientProtocolException] XXXXXXXXXXXXXXXXXXXXX.XXXXXXX.XXXX failed to respond"}
[2021-12-24T02:26:59,139][ERROR][logstash.outputs.Elasticsearch] Encountered a retryable error. Will Retry with exponential backoff {:code=\>500,
[ERROR][org.logstash.execution.WorkerLoop] Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash.
java.lang.NullPointerException: null
Please help me to solve this issue to the complete...
You can provide me a time slot when you will be available so that i can troubleshoot this continously without any time gaping.......
---
### Author:  [@d6036de2b54af16665f4](https://discuss.elastic.co/u/d6036de2b54af16665f4)
#### Post date: [December 31, 2021, 1:28pm UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/4 "2021-12-31T13:28:28Z")
Only One date of data is showing with this query but More data is also got uploded on the same logstash machine...
---
### Author:  [@Petr.Simik](https://discuss.elastic.co/u/Petr.Simik)
#### Post date: [January 2, 2022, 6:49pm UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/5 "2022-01-02T18:49:29Z")
to check if Elasticsearch in available just type curl localhost:9200
and check if it gets any output
what is the RAM size of node where Elastic is running?
How did you set Heap size?
running logstash on the same machine is a common practice - not a problem
---
### Author:  [@Petr.Simik](https://discuss.elastic.co/u/Petr.Simik)
#### Post date: [January 2, 2022, 6:52pm UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/6 "2022-01-02T18:52:16Z")
you can also troibleshoot it by manually POST one of the logstash parsed event to elasticsearch
1. print one event to screen
2. try to curl -x POST the event to Elasticsearch
see [Create a new document in the index | Elasticsearch API documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-index_.html)
POST my-index-000001/\_doc/
{
### your event
}
---
### Author:  [@d6036de2b54af16665f4](https://discuss.elastic.co/u/d6036de2b54af16665f4)
#### Post date: [January 3, 2022, 7:54am UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/7 "2022-01-03T07:54:11Z")
when i run curl localhost:9200 i got connection refused error...
But, when i used
curl [http://XXXXXXX-XXXXXX-XXXXXX-XXX-elb-XXXXXXXXXXXXaws.com:9200](http://XXXXXXX-XXXXXX-XXXXXX-XXX-elb-XXXXXXXXXXXXaws.com:9200) {
"name" : "ip-XXX-XX-X-XX.ec2.XXXXXXl",
"cluster\_name" : "cluster name",
"cluster\_uuid" : "XVHHSHD3QDtyessZOwenklaewq",
"version" : {
"number" : "7.1.0",
"build\_flavor" : "default",
"build\_type" : "rpm",
"build\_hash" : "606a173",
"build\_date" : "2019-05-16T00:43:15.323135Z",
"build\_snapshot" : false,
"lucene\_version" : "8.0.0",
"minimum\_wire\_compatibility\_version" : "6.8.0",
"minimum\_index\_compatibility\_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
\*\*\* The instance where Elasticsearch is running is 8gb and 1 gb medium type....
\*\*\* i think the heap size is being set by jvm.options
---
### Author:  [@d6036de2b54af16665f4](https://discuss.elastic.co/u/d6036de2b54af16665f4)
#### Post date: [January 4, 2022, 7:38am UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/9 "2022-01-04T07:38:46Z")
Any update?
---
### Author:  [@Petr.Simik](https://discuss.elastic.co/u/Petr.Simik)
#### Post date: [January 4, 2022, 9:12am UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/10 "2022-01-04T09:12:52Z")
> [@d6036de2b54af16665f4](#):
>
> so gratefull of you if you get connected for short time period for this
Sorry I am not support expert - you should contact someone from Elatic if you have the License.
I am just another user of Elasticsearch like you.
You are mixing up several problems
lets resolve them separately
1. Elasticsearch is up and running and can index new data
this problem you tested by curl commands I send you. Did you try curl POST - did it index new data to elasticsearch?
If yes - there is no problem with elasticsearch
btw you did not respond to HEAP size in /etc/elasticsearch/jvm.option file
-XmsXXg
-XmxYYg
however if elasticsearch is running and can index the data I do not see a problem here
1. problems with logstash
I see this might be a problem.
did you try to index simple piece of data to Elastic by Logstash
try to index static single event value
if this works the problem might be in logstash yaml parser code
provide your code here so the community can help you
1. Logstash problem
---
### Author:  [@d6036de2b54af16665f4](https://discuss.elastic.co/u/d6036de2b54af16665f4)
#### Post date: [January 4, 2022, 9:20am UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/11 "2022-01-04T09:20:20Z")
Elasticsearch is running yes it is indexing to new data in ES.
-Xms1g
-Xms1g
is heap size in Es jvm.options
yes i tried to index small piece of data from logstash to ES and it worked...
Then what can be the issue and what code i may help you... to identify it
thanks
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 1, 2022, 9:20am UTC](https://discuss.elastic.co/t/data-not-visibile-in-kibana/293122/12 "2022-02-01T09:20:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.