# Elasticsearch/Kibana 7.8.0-1 in Docker Container - Index Pattern issue in Kibana as nothing showing up when going into Discover
**URL:** https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088
**Category:** Kibana
**Created:** [July 7, 2020, 4:51am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088 "2020-07-07T04:51:53Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@soneill](https://discuss.elastic.co/u/soneill)
#### Post date: [July 7, 2020, 4:51am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088/1 "2020-07-07T04:51:53Z")
I have Elasticsearch and Kibana running in a docker container. I've recently setup up a data stream from my 1900ACS router of ulog data pushing connections information from that router into Elasticsearch. From what I'm seeing in Elasticsearch, an index has been created and data exists within it.
My issue seems to be within Kibana, creating an Index Pattern doesn't show anything. Using the Kibana DevTools, I can see data exists like the following:
```
{
"_index" : "network-2020-07-06",
"_type" : "_doc",
"_id" : "gg5dJ3MB_VGq9xsppnf1",
"_score" : 1.0,
"_source" : {
"tags" : "openwrt",
"outbound" : {
"source" : {
"port" : "55147",
"packets" : "11",
"ip" : "192.168.1.247",
"bytes" : "3036"
},
"destination" : {
"port" : "443",
"ip" : "52.206.227.240",
"geo" : {
"region_name" : "Virginia",
"region_iso_code" : "VA",
"location" : "39.048100,-77.472800",
"country_name" : "United States",
"country_iso_code" : "US",
"continent_name" : "North America",
"city_name" : "Ashburn"
},
"address" : "ec2-52-206-227-240.compute-1.amazonaws.com"
}
},
"network" : {
"transport" : "TCP"
},
"message" : """Session completed; client='192.168.1.247'; server='52.206.227.240'; destination_port='443; protocol='TCP'; session_lenght='75'""",
"inbound" : {
"source" : {
"port" : "443",
"packets" : "8",
"ip" : "52.206.227.240",
"bytes" : "4393"
},
"destination" : {
"port" : "55147",
"ip" : "173.#.#.#"
}
},
"host" : {
"name" : "LEDE",
"ip" : "192.168.1.1"
},
"event" : {
"start" : "2020-07-06T22:41:10-07:00",
"end" : "2020-07-06T22:42:25-07:00",
"duration" : "75"
},
"ecs" : {
"version" : "1.0.0"
},
"@timestamp" : "2020-07-06T22:42:25-07:00"
}
},
```
However, after creating an Index Pattern in Kibana of simply "network-\*", I'm getting nothing in Discover though. I'm getting this error:
```
No results match your search criteria
```
Nothing really sure what is going on. Any ideas ?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 7, 2020, 4:54am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088/2 "2020-07-07T04:54:41Z")
Is the timepicker set to the right range? By default it's the last 15 minutes.
---
### Author:  [@soneill](https://discuss.elastic.co/u/soneill)
#### Post date: [July 7, 2020, 5:19am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088/3 "2020-07-07T05:19:51Z")
Yes, I have even changed it to 15 hours ago to Now with the same result.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 7, 2020, 5:24am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088/4 "2020-07-07T05:24:13Z")
In the index settings page in Kibana, what field is set as the timestamp one?
---
### Author:  [@soneill](https://discuss.elastic.co/u/soneill)
#### Post date: [July 7, 2020, 5:38am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088/5 "2020-07-07T05:38:59Z")
Time Filter field name: '@timestamp'
---
### Author:  [@soneill](https://discuss.elastic.co/u/soneill)
#### Post date: [July 7, 2020, 11:25pm UTC](https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088/6 "2020-07-07T23:25:21Z")
This is interesting. I waited to see what would happen after a new index was created for today. Now data is showing up in Discover. BUT, the data for yesterday still isn't showing in Discover even though there is an index for it. The data for today starts at exactly 12 midnight.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 4, 2020, 11:25pm UTC](https://discuss.elastic.co/t/elasticsearch-kibana-7-8-0-1-in-docker-container-index-pattern-issue-in-kibana-as-nothing-showing-up-when-going-into-discover/240088/7 "2020-08-04T23:25:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.