# Problem Couldn't find any Elasticsearch data

**URL:** <https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798>\
**Category:** Elasticsearch\
**Created:** [April 28, 2019, 10:47am UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798 "2019-04-28T10:47:43Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 28, 2019, 10:47am UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/1 "2019-04-28T10:47:43Z")

</div>

hi my friend, i installed ealstichsearch, logstach, kibana and filebeat on the same server but my problem is that cant visulaize my data in kibana, when tryin to create an index ig give me an error "Couldn't find any Elasticsearch data" when i try to check : [http://localhost:9200/\_cat/indices?v](http://localhost:9200/_cat/indices?v) i cant see logstach indice ![kebanaerror](https://us1.discourse-cdn.com/elastic/original/3X/2/1/21a2c21f71a081196f803cd8754ad53226a6b306.png) ![logstach%20index](https://us1.discourse-cdn.com/elastic/original/3X/7/2/72012c2fc8dadbc37b542d871ef4968a04fc34dc.png)

---

<div class="post-metadata">

**Author:** ![staodd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/staodd/32/24509_2.png) [@staodd](https://discuss.elastic.co/u/staodd)\
**Post date:** [April 28, 2019, 2:45pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/2 "2019-04-28T14:45:18Z")

</div>

You are not giving anyone anything to work with. No information on your environment or anything. Please include as much information as possible. OS, versions, logs, etc....  
Have you even set up logstash to ingest any files? Or filebeat?

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 28, 2019, 3:05pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/3 "2019-04-28T15:05:58Z")

</div>

i follwed this tutoriel ([https://www.howtoforge.com/tutorial/how-to-install-elastic-stack-on-ubuntu-16-04/](https://www.howtoforge.com/tutorial/how-to-install-elastic-stack-on-ubuntu-16-04/) )and have done the configuration just i chaged elk-master with localhost  
[https://www.howtoforge.com/tutorial/how-to-install-elastic-stack-on-ubuntu-16-04/](https://www.howtoforge.com/tutorial/how-to-install-elastic-stack-on-ubuntu-16-04/)

---

<div class="post-metadata">

**Author:** ![staodd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/staodd/32/24509_2.png) [@staodd](https://discuss.elastic.co/u/staodd)\
**Post date:** [April 28, 2019, 3:19pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/4 "2019-04-28T15:19:45Z")

</div>

You still don't give us any logs or anything. Please read instructions on how to format logs/code using format codes and post them.

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 28, 2019, 3:28pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/5 "2019-04-28T15:28:41Z")

</div>

i have no error just in kibana it show the message mentionned in the first post there is n error i checked logstch is runing , same thing for elastichsearch, nginx and filebeat

---

<div class="post-metadata">

**Author:** ![Bernt\_Rostad](https://avatars.discourse-cdn.com/v4/letter/b/3ab097/32.png) [@Bernt\_Rostad](https://discuss.elastic.co/u/Bernt_Rostad)\
**Post date:** [April 29, 2019, 8:05am UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/6 "2019-04-29T08:05:02Z")

</div>

It looks to me like what you're trying to create is an **index pattern** , not an index, and as explained in the [tutorial](https://www.elastic.co/guide/en/kibana/current/tutorial-define-index.html):

> When you define an index pattern, the indices that match that pattern must exist in Elasticsearch and they must contain data.

So you will first have to start up Logstash and (or) Filebeat in order to create and populate logstash-YYYY.MMM.DD and filebeat-YYYY.MMM.DD indices in your Elasticsearch instance. After that you can create index patterns for these indices in Kibana.

Good luck!

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 29, 2019, 2:25pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/7 "2019-04-29T14:25:01Z")

</div>

before coonecting to bibana i have already started Logstash , Filebeat and elsatic search, but i have the same problem i cant see filebeat index i find only kibana indexes

---

<div class="post-metadata">

**Author:** ![Bernt\_Rostad](https://avatars.discourse-cdn.com/v4/letter/b/3ab097/32.png) [@Bernt\_Rostad](https://discuss.elastic.co/u/Bernt_Rostad)\
**Post date:** [April 29, 2019, 2:51pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/8 "2019-04-29T14:51:07Z")

</div>

> [@kumar4](#):
>
> i have already started Logstash , Filebeat and elsatic search, but i have the same problem i cant see filebeat index i find only kibana indexes

Then I would guess that there is a problem with the configuration of Logstash and Metricbeat or that there is a firewall stopping them from indexing data into Elasticsearch.

Perhaps you could try to run Metricbeat manually to see what kind of errors you get? Something like this:

`metricbeat -e -c metricbeat.yml`

When I run it manually I get information about host and port number that Metricbeat connects to, and if a connection was established:

```
2019-04-29T16:42:34.667+0200 INFO pipeline/output.go:95 Connecting to backoff(async(tcp://es-host:5044))
2019-04-29T16:42:34.696+0200 INFO pipeline/output.go:105 Connection to backoff(async(tcp://es-host:5044)) established

```

I hope you can get some useful error messages this way.

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 29, 2019, 6:37pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/9 "2019-04-29T18:37:45Z")

</div>

but in my configuration i use filebeat not metricbeat, so can i use metricbeat even if i didnt insall it and what where the file metricbeat.yml situated

---

<div class="post-metadata">

**Author:** ![Bernt\_Rostad](https://avatars.discourse-cdn.com/v4/letter/b/3ab097/32.png) [@Bernt\_Rostad](https://discuss.elastic.co/u/Bernt_Rostad)\
**Post date:** [April 29, 2019, 6:57pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/10 "2019-04-29T18:57:06Z")

</div>

> [@kumar4](#):
>
> but in my configuration i use filebeat not metricbeat,

Sorry, I forgot that. I have not used Filebeat but I assume you can run that manually too and get better error messages.

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 29, 2019, 7:03pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/11 "2019-04-29T19:03:56Z")

</div>

but in my configuration i use filebeat not metricbeat, so can i use metricbeat even if i didnt insall it and what where the file metricbeat.yml situatedbut in my configuration i use filebeat not metricbeat, so can i use metricbeat even if i didnt insall it and what where the file metricbeat.yml situated;this what i obteain when i chek the status of and the content of filebeat.yml ,logstash.yml ,elastichsearxh.yml and kibana.yml

 ![elasticstatus](https://us1.discourse-cdn.com/elastic/original/3X/4/7/470556a78d863e59cdc5c0a44db9d1e38bf279cf.png) ![folbeat%20status](https://us1.discourse-cdn.com/elastic/original/3X/d/c/dc4514481a1f2461463f076fb99c4d22404de34f.png) ![lostashstatus](https://us1.discourse-cdn.com/elastic/original/3X/3/d/3d7254bbc5bd0faa273c7f135fb54ae6c2bb3ae8.png)

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 29, 2019, 7:06pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/12 "2019-04-29T19:06:06Z")

</div>

this is kibana.yml

# Kibana is served by a back end server. This setting specifies the port to use.

server.port: 5601

# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.

# The default is 'localhost', which usually means remote machines will not be able to connect.

# To allow connections from remote users, set this parameter to a non-loopback address.

server.host: "localhost"  
elasticsearch.url: "[http://localhost:9200](http://localhost:9200)"

# Enables you to specify a path to mount Kibana at if you are running behind a proxy.

# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath

# from requests it receives, and to prevent a deprecation warning at startup.

# This setting cannot end in a slash.

#server.basePath: ""

# Specifies whether Kibana should rewrite requests that are prefixed with

# `server.basePath` or require that they are rewritten by your reverse proxy.

# This setting was effectively always `false` before Kibana 6.3 and will

# default to `true` starting in Kibana 7.0.

#server.rewriteBasePath: false

# The maximum payload size in bytes for incoming server requests.

#server.maxPayloadBytes: 1048576

# The Kibana server's name. This is used for display purposes.

#server.name: "your-hostname"

# The URLs of the Elasticsearch instances to use for all your queries.

#elasticsearch.hosts: ["[http://localhost:9200](http://localhost:9200)"]

# When this setting's value is true Kibana uses the hostname specified in the server.host

# setting. When the value of this setting is false, Kibana uses the hostname of the host

# that connects to this Kibana instance.

#elasticsearch.preserveHost: true

# Kibana uses an index in Elasticsearch to store saved searches, visualizations and

# dashboards. Kibana creates a new index if the index doesn't already exist.

#kibana.index: ".kibana"

# The default application to load.

#kibana.defaultAppId: "home"

# If your Elasticsearch is protected with basic authentication, these settings provide

# the username and password that the Kibana server uses to perform maintenance on the Kibana

# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which

# is proxied through the Kibana server.

#elasticsearch.username: "user"  
#elasticsearch.password: "pass"

# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.

# These settings enable SSL for outgoing requests from the Kibana server to the browser.

#server.ssl.enabled: false  
#server.ssl.certificate: /path/to/your/server.crt  
#server.ssl.key: /path/to/your/server.key

# Optional settings that provide the paths to the PEM-format SSL certificate and key files.

# These files validate that your Elasticsearch backend uses the same key files.

#elasticsearch.ssl.certificate: /path/to/your/client.crt  
#elasticsearch.ssl.key: /path/to/your/client.key

# Optional setting that enables you to specify a path to the PEM file for the certificate

# authority for your Elasticsearch instance.

#elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"]

# To disregard the validity of SSL certificates, change this setting's value to 'none'.

#elasticsearch.ssl.verificationMode: full

# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of

# the elasticsearch.requestTimeout setting.

#elasticsearch.pingTimeout: 1500

# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value

# must be a positive integer.

#elasticsearch.requestTimeout: 30000

# List of Kibana client-side headers to send to Elasticsearch. To send _no_ client-side

# headers, set this value to (an empty list).

#elasticsearch.requestHeadersWhitelist: [authorization]

# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten

# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.

#elasticsearch.customHeaders: {}

# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.

#elasticsearch.shardTimeout: 30000

# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.

#elasticsearch.startupTimeout: 5000

# Logs queries sent to Elasticsearch. Requires logging.verbose set to true.

#elasticsearch.logQueries: false

# Specifies the path where Kibana creates the process ID file.

#pid.file: /var/run/kibana.pid

# Enables you specify a file where Kibana stores log output.

#logging.dest: stdout

# Set the value of this setting to true to suppress all logging output.

#logging.silent: false

# Set the value of this setting to true to suppress all logging output other than error messages.

#logging.quiet: false

# Set the value of this setting to true to log all events, including system usage information

# and all requests.

#logging.verbose: false

# Set the interval in milliseconds to sample system and process performance

# metrics. Minimum is 100ms. Defaults to 5000.

#ops.interval: 5000

# Specifies locale to be used for all localizable strings, dates and number formats.

#i18n.locale: "en"

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 29, 2019, 7:07pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/13 "2019-04-29T19:07:35Z")

</div>

this is what i have done in the first section of filebeat.yml  
filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so

# you can use different inputs for various configurations.

# Below are the input specific configurations.

- type: log

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 29, 2019, 7:10pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/14 "2019-04-29T19:10:10Z")

</div>

logstash.yml is :  
path.data: /var/lib/logstash  
path.logs: /var/log/logstash

---

<div class="post-metadata">

**Author:** ![kumar4](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar4/32/48326_2.png) [@kumar4](https://discuss.elastic.co/u/kumar4)\
**Post date:** [April 29, 2019, 7:17pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/15 "2019-04-29T19:17:22Z")

</div>

here are the diffrents files : inoput filter and outpout :

 ![inputfilteroutput](https://us1.discourse-cdn.com/elastic/original/3X/c/c/ccb208119aa959100d36fc1031e11084d598043d.png)

---

<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:** [May 27, 2019, 7:26pm UTC](https://discuss.elastic.co/t/problem-couldnt-find-any-elasticsearch-data/178798/16 "2019-05-27T19:26:07Z")

</div>

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