# Missing index pattern heartbeat-\* **URL:** \ **Category:** Beats\ **Tags:** heartbeat\ **Created:** [September 3, 2020, 1:37pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394 "2020-09-03T13:37:02Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ManuelF](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@ManuelF](https://discuss.elastic.co/u/ManuelF)\ **Post date:** [September 3, 2020, 1:37pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394/1 "2020-09-03T13:37:02Z")
Hi, I am using ELK 7.9. I have installed and confirmed working fine Winlogbeat, Packetbeat and Auditbeat. But regarding Heartbeat, apparently is working fine, as is communicating with Elasticsearch, but is the only beat that is not creating the it's own index as expected (heartbeat-\*). Because of this I cannot use Discovery with Heartbeat, because index is not available. Other queries related cannot be done either. - Legacy Index Template `heartbeat-7.9.0-*` is created - Under Index Management is created `heartbeat-7.9.0-[date]-000001` - Under Index Pattern is missing `heartbeat-*` - Under Discovery is missing `heartbeat-*` I have ran heartbeat setup several times. The above issue was also exposed and discussed [here](https://github.com/elastic/beats/issues/15341), by **[DanRoscigno](https://github.com/DanRoscigno)**, but I did not see the solution. Maybe I missed. > Maybe this is related to another issue I am seeing with heartbeat. Running `heartbeat setup` should probably be setting up the index pattern `heartbeat-*` . Instead, it is setting up the index pattern `UptimeIndexPattern` which does not seem to work with anything other than the Uptime UI (for example, you cannot use it in Discover or Lens). Is there anything I can do to fix this? Thank you ---
**Author:** ![shahzad31](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shahzad31/32/51637_2.png) [@shahzad31](https://discuss.elastic.co/u/shahzad31)\ **Post date:** [September 4, 2020, 2:16pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394/2 "2020-09-04T14:16:51Z")
Hi @ManuelF can you please clarify if you mean heartbeat isn't creating `heartbeat-*` index pattern or do you mean heartbeat isn't publishing data? If you want to see heartbeat data in Discover, you can yourself create an index pattern using kibana if data is being published. Also you can use Uptime app to visualize heartbeat data. Regards ---
**Author:** ![ManuelF](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@ManuelF](https://discuss.elastic.co/u/ManuelF)\ **Post date:** [September 4, 2020, 2:52pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394/3 "2020-09-04T14:52:24Z")
Hi @shahzad31, Thank you for answering. Heartbeat is sending data to Elasticsearch that is only available from Uptime UI, but the index `heartbeat-*` is not being created and I would like to used like in the past I used to. > Maybe this is related to another issue I am seeing with heartbeat. Running `heartbeat setup` should probably be setting up the index pattern `heartbeat-*` . Instead, it is setting up the index pattern `UptimeIndexPattern` which does not seem to work with anything other than the Uptime UI (for example, you cannot use it in Discover or Lens). ---
**Author:** ![shahzad31](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shahzad31/32/51637_2.png) [@shahzad31](https://discuss.elastic.co/u/shahzad31)\ **Post date:** [September 4, 2020, 3:19pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394/4 "2020-09-04T15:19:28Z")
Great @ManuelF , you can create that yourself easily, we are not creating an uptime index pattern auto anymore. You can go `stack management` in kibana go to index patterns , this may differ based on diff kibana versions, i am using master ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/6/1676b5991e157d723c2a4402d57194d666a867b0.png) Press 'Create index pattern' , in next screen give it a name 'heartbeat-\*' ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/f/ff6ef16f7f4eb92933246a140d0fc38b2ca5931e.png) then choose @timestamp as Time field ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/1/0196d920115f8aa59783b3c641d1f37a8317efb0.png) and you are done. Go to Discover app, you should see the pattern and data. ---
**Author:** ![ManuelF](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@ManuelF](https://discuss.elastic.co/u/ManuelF)\ **Post date:** [September 4, 2020, 3:31pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394/5 "2020-09-04T15:31:50Z")
Hi @shahzad31, The solution provided worked perfectly! 😀 Thank you very much! ---
**Author:** ![shahzad31](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shahzad31/32/51637_2.png) [@shahzad31](https://discuss.elastic.co/u/shahzad31)\ **Post date:** [September 4, 2020, 7:09pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394/6 "2020-09-04T19:09:44Z")
I am glad it did. Though @ManuelF I am curious why you use Discover app instead of uptime to view heartbeat data? ---
**Author:** ![ManuelF](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@ManuelF](https://discuss.elastic.co/u/ManuelF)\ **Post date:** [September 4, 2020, 9:08pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394/7 "2020-09-04T21:08:40Z")
Actually I use Discover, mostly for: 1- Checking the data is arriving to Elasticsearch 2- Checking fields values and other details 3- To build filters and queries ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 2, 2020, 11:08pm UTC](https://discuss.elastic.co/t/missing-index-pattern-heartbeat/247394/8 "2020-10-02T23:08:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.