# Filebeat-\* index pattern (Can´t find it!)

**URL:** https://discuss.elastic.co/t/filebeat-index-pattern-can-t-find-it/256208
**Category:** Kibana
**Created:** [November 21, 2020, 1:35am UTC](https://discuss.elastic.co/t/filebeat-index-pattern-can-t-find-it/256208 "2020-11-21T01:35:14Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![771M771](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/771m771/32/79434_2.png) [@771M771](https://discuss.elastic.co/u/771M771)
#### Post date: [November 21, 2020, 1:35am UTC](https://discuss.elastic.co/t/filebeat-index-pattern-can-t-find-it/256208/1 "2020-11-21T01:35:14Z")

</div>

I´ve installed and configured ELK (elasticsearch, logstash, kibana, and filebeat) and they are up and running on localhost:ports. But when I try to create an index pattern in Kibana after uploading my .json it can´t find "filebeat-\*".

I tried to add another index pattern that matches the source and I get one step further but when I try to add timefield using the list I get "Error Too Many Requests".

Why isn´t Kibana finding "filebeat-\*"?

//Ubernoob

---

<div class="post-metadata">

### Author: ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)
#### Post date: [November 21, 2020, 3:10am UTC](https://discuss.elastic.co/t/filebeat-index-pattern-can-t-find-it/256208/2 "2020-11-21T03:10:14Z")

</div>

Hello @771M771

Which version of the stack are you using?

Try running `GET /_cat/indices` from kibana dev tools. What is the output?

Thanks,  
Matt

---

<div class="post-metadata">

### Author: ![771M771](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/771m771/32/79434_2.png) [@771M771](https://discuss.elastic.co/u/771M771)
#### Post date: [November 21, 2020, 4:08am UTC](https://discuss.elastic.co/t/filebeat-index-pattern-can-t-find-it/256208/3 "2020-11-21T04:08:35Z")

</div>

Hi Matt.  
Thanks for the fast response!

When I run `GET /_cat/indices` in dev tools i get this output:

```auto
green open apm-7.10.0-profile-000001 AA3s9M45RvO7h3AH7Csiog 1 1 0 0 416b 208b
green open apm-7.10.0-error-000001 EZOvMNRrTXu7U4xrPP5XiA 1 1 0 0 416b 208b
green open .apm-agent-configuration VTMF6ecaQ_SGkbKm8MazMA 1 1 0 0 416b 208b
green open apm-7.10.0-metric-000001 wviQ5UJ4R-G7SKxbT_YSQw 1 1 0 0 416b 208b
green open .kibana_1 gKazcIycRdOrICUXLSQp2g 1 1 9 1 20.7mb 10.3mb
green open .security-tokens-7 pPO3YnuSTJuct1u3FlrkQQ 1 1 1 0 19.3kb 9.6kb
green open apm-7.10.0-span-000001 mQNaGZ3jQD6vV-zr4zUF3Q 1 1 0 0 416b 208b
green open .security-7 KW-r0_UZSMS2P-XbfNgI8g 1 1 56 1 292.5kb 146kb
green open .apm-custom-link shsL16-pS6aeMPvZsJrteQ 1 1 0 0 416b 208b
green open .kibana_task_manager_1 oFCDrFh_RMi9EIeSJ88mJg 1 1 6 21 171.1kb 98.6kb
green open apm-7.10.0-onboarding-2020.11.21 w4xAhu7iRc-EoNO1mXeCTg 1 1 1 0 14.8kb 7.3kb
green open apm-7.10.0-transaction-000001 BDRytNDmQLm1BnmMa8lftA 1 1 0 0 416b 208b
green open .kibana-event-log-7.10.0-000001 3hFc-vqJTH6tq9CiCLp50A 1 1 2 0 21.7kb 10.8kb

```

(I have no idea if I did this right...)

---

<div class="post-metadata">

### Author: ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)
#### Post date: [November 21, 2020, 4:43am UTC](https://discuss.elastic.co/t/filebeat-index-pattern-can-t-find-it/256208/4 "2020-11-21T04:43:24Z")

</div>

@771M771 You did it exactly right. I see a number of `apm-* ` indices but I don't see any filebeat indices. Next step would be to look at the filebeat logs and figure out why data isn't being sent over.

---

<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: [December 19, 2020, 4:43am UTC](https://discuss.elastic.co/t/filebeat-index-pattern-can-t-find-it/256208/5 "2020-12-19T04:43:26Z")

</div>

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