# Kibana Uptime having an issue (unknown type for collapse field \`monitor.id\`)

**URL:** https://discuss.elastic.co/t/kibana-uptime-having-an-issue-unknown-type-for-collapse-field-monitor-id/185511
**Category:** Beats
**Tags:** heartbeat
**Created:** [June 12, 2019, 8:45pm UTC](https://discuss.elastic.co/t/kibana-uptime-having-an-issue-unknown-type-for-collapse-field-monitor-id/185511 "2019-06-12T20:45:11Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![vijayakrishna.rg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijayakrishna.rg/32/36798_2.png) [@vijayakrishna.rg](https://discuss.elastic.co/u/vijayakrishna.rg)
#### Post date: [June 12, 2019, 8:45pm UTC](https://discuss.elastic.co/t/kibana-uptime-having-an-issue-unknown-type-for-collapse-field-monitor-id/185511/1 "2019-06-12T20:45:11Z")

</div>

Hi,

i am having an issue while configure Heartbeat to setup uptime in kibana, it says "Error GraphQL error: [search\_context\_exception] unknown type for collapse field `monitor.id`,", can someone please help me with it, thanks.

 ![55%20PM](https://us1.discourse-cdn.com/elastic/original/3X/5/0/50e0fd2ce2b0741876e03b9fe4fd95a2981d64e1.png)

When i looked at Heartbeat index "monitor.id" has same as "monitor.host"

 ![heartbat-index](https://us1.discourse-cdn.com/elastic/original/3X/e/1/e12f4687b603267089629d8bee7921c88ad2320a.jpeg)

error.type has "io", not sure what do with it.

 ![58%20PM](https://us1.discourse-cdn.com/elastic/original/3X/b/3/b3c25266648f1e9b98089b87d9d37cacc43e4bf6.png)

---

<div class="post-metadata">

### Author: ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [June 12, 2019, 9:00pm UTC](https://discuss.elastic.co/t/kibana-uptime-having-an-issue-unknown-type-for-collapse-field-monitor-id/185511/2 "2019-06-12T21:00:21Z")

</div>

This is likely due to deleting heartbeat indices while heartbeat is running.

To fix it:

1. Stop heartbeat
2. Delete all heartbeat indices
3. Start heartbeat

---

<div class="post-metadata">

### Author: ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [June 12, 2019, 9:00pm UTC](https://discuss.elastic.co/t/kibana-uptime-having-an-issue-unknown-type-for-collapse-field-monitor-id/185511/3 "2019-06-12T21:00:34Z")

</div>

Note that this will of course delete all monitoring data

---

<div class="post-metadata">

### Author: ![vijayakrishna.rg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijayakrishna.rg/32/36798_2.png) [@vijayakrishna.rg](https://discuss.elastic.co/u/vijayakrishna.rg)
#### Post date: [June 12, 2019, 9:01pm UTC](https://discuss.elastic.co/t/kibana-uptime-having-an-issue-unknown-type-for-collapse-field-monitor-id/185511/4 "2019-06-12T21:01:57Z")

</div>

i have deleted all heartbeat indices multiple times after stoping heartbeat service, still has same issue.

---

<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: [July 10, 2019, 9:02pm UTC](https://discuss.elastic.co/t/kibana-uptime-having-an-issue-unknown-type-for-collapse-field-monitor-id/185511/5 "2019-07-10T21:02:03Z")

</div>

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