# No uptime monitors found after upgrading to 8.8.2
**URL:** https://discuss.elastic.co/t/no-uptime-monitors-found-after-upgrading-to-8-8-2/341998
**Category:** Kibana
**Created:** [August 30, 2023, 6:47pm UTC](https://discuss.elastic.co/t/no-uptime-monitors-found-after-upgrading-to-8-8-2/341998 "2023-08-30T18:47:09Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@tecbox41](https://discuss.elastic.co/u/tecbox41)
#### Post date: [August 30, 2023, 6:47pm UTC](https://discuss.elastic.co/t/no-uptime-monitors-found-after-upgrading-to-8-8-2/341998/1 "2023-08-30T18:47:09Z")
Recently upgraded from Elasticsearch 7.16.2 to 8.8.2 and Uptime now shows "_No uptime monitors found_" for Monitors. I ran the setup for heartbeat once I upgraded it to 8.8.2 and the index template & data stream got created. I am able to see the new heartbeat indexes in Index Management with docs and several hundred MB of data and am able to query the data in Discover. As a troubleshooting step, I stopped heartbeat, removed all the old heartbeat 7 indexes/streams/templates and all the new heartbeat 8 indexes/streams/templates, re-ran the setup, and re-started heartbeat. This successfully re-created the template & stream, but still no monitors show up.
We are utilizing Logstash on a remote host, so I also tried to load the index template manually by performing the following:
Export the index template (from the heartbeat server):
`./heartbeat export template > heartbeat.template.json`
Installed the template (from the coordinating server):
`curl -XPUT -H 'Content-Type: application/json' http://localhost:9200/_index_template/heartbeat-8.8.2 -d@heartbeat.template.json`
Loaded the data stream (from the coordinating server):
`curl -XPUT http://localhost:9200/_data_stream/heartbeat-8.8.2`
Still no monitors showing up. The monitors were showing up fine prior to upgrading to 8.8.2.
I am on CentOS 7 and the heartbeat.yml is as follows:
```auto
path.home: /apps/heartbeat/heartbeat-8.8.2
path.config: ${path.home}/config
heartbeat.config.monitors:
path: ${path.home}/monitors.d/*.yml
reload.enabled: true
reload.period: 60s
setup.template.settings:
template.fields: "${path.config}/fields.yml"
index.number_of_shards: 1
index.number_of_replicas: 2
index.codec: best_compression
output.redis:
hosts: ["logstash01:6379"]
key: heartbeat
datatype: list
logging.level: info
logging.selectors: ["*"]
logging.json: true
logging.files:
path: ${HEARTBEAT_HOME}/logs
name: heartbeat.log
keepfiles: 7
http.enabled: true
```
Any help would be appreciated!
Thanks.
---
### Author:  [@chouben](https://discuss.elastic.co/u/chouben)
#### Post date: [August 31, 2023, 1:43pm UTC](https://discuss.elastic.co/t/no-uptime-monitors-found-after-upgrading-to-8-8-2/341998/2 "2023-08-31T13:43:44Z")
> [@tecbox41](#):
>
> I am able to see the new heartbeat indexes in Index Management with docs and several hundred MB of data and am able to query the data in Discover.
Could you provide full screen screenshots of both (Discover & Uptime), with exact the same time window?
Could you also confirm settings are pointing to your hearbeat indices?
---
### Author:  [@tecbox41](https://discuss.elastic.co/u/tecbox41)
#### Post date: [August 31, 2023, 6:39pm UTC](https://discuss.elastic.co/t/no-uptime-monitors-found-after-upgrading-to-8-8-2/341998/3 "2023-08-31T18:39:19Z")
@chouben...thanks so much for taking the time to respond.
I believe I determined what the problem was. Since we are sending to Logstash, I had to update the index name in the Logstash heartbeat.cfg file
from
`index => "heartbeat-%{[@metadata][version]}-%{+YYYY.MM.dd}"`
to
`index => "heartbeat-%{[@metadata][version]}"`
Once I did this and restarted Logstash, my monitors were showing up.
---
### Author:  [@chouben](https://discuss.elastic.co/u/chouben)
#### Post date: [September 1, 2023, 6:54am UTC](https://discuss.elastic.co/t/no-uptime-monitors-found-after-upgrading-to-8-8-2/341998/4 "2023-09-01T06:54:24Z")
If settings allow this pattern, you should be fine too!
> [@tecbox41](#):
>
> heartbeat-%{[@metadata][version]}-%{+YYYY.MM.dd}
PS: Don't forget to mark a thread as resolved, once it's done 😉
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 29, 2023, 6:54am UTC](https://discuss.elastic.co/t/no-uptime-monitors-found-after-upgrading-to-8-8-2/341998/5 "2023-09-29T06:54:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.