# 6.6 upgrade to 6.7 on Elastic Cloud Uptime data not showing **URL:** \ **Category:** Synthetics\ **Created:** [April 2, 2019, 1:29pm UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004 "2019-04-02T13:29:22Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\ **Post date:** [April 2, 2019, 1:29pm UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004/1 "2019-04-02T13:29:22Z")
We upgraded from 6.6 to 6.7 on Elastic Cloud Elasticsearch and Kibana. Then upgraded heartbeat on our internal vm's shipping to logstash. We also re-created the heartbeat template from the heartbeat 6.7 home. The Uptime page shows in kibana but no data is viewable. Thanks ---
**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\ **Post date:** [April 2, 2019, 2:45pm UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004/2 "2019-04-02T14:45:46Z")
Elasticsearch is receiving docs from heartbeat... "{ "\_index": "heartbeat-6.6.0-2019.04.02", "\_type": "doc", "\_id": "EfuA3mkB0iONRnXhVGDt", "\_version": 1, "\_score": null, "\_source": { "@timestamp": "2019-04-02T14:42:25.000Z", "tags": [ "beats\_input\_raw\_event" ], "resolve": { "host": "rrc101-196516-webui", "rtt": { "us": 781 }, "ip": "10.142.0.5" }, "@version": "1", "event": { "dataset": "uptime" }, "host": { "name": "rrc101-196516-webui" }, "requests": 1, "monitor": { "status": "up", "ip": "10.142.0.5", "id": "icmp-icmp-host-ip@rrc101-196516-webui", "host": "rrc101-196516-webui", "duration": { "us": 914 }, "name": "icmp", "type": "icmp" }, "beat": { "hostname": "rrc101-196516-webui", "name": "rrc101-196516-webui", "version": "6.7.0" }, "rtt": { "us": 66 } }, "fields": { "@timestamp": [ "2019-04-02T14:42:25.000Z" ] }, "sort": [ 1554216145000 ] }" ---
**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\ **Post date:** [April 2, 2019, 9:45pm UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004/3 "2019-04-02T21:45:15Z")
I changed logstash to send a 6.7 index name and created a new pattern: heartbeat-6.7.0-\*\* Here is the new json in discover: " { "\_index": "heartbeat-6.7.0-2019.04.02", "\_type": "doc", "\_id": "uSwC4GkB0iONRnXhJm95", "\_version": 1, "\_score": null, "\_source": { "@version": "1", "tls": { "certificate\_not\_valid\_after": "2019-04-27T23:59:59.000Z", "certificate\_not\_valid\_before": "2016-01-28T00:00:00.000Z", "rtt": { "handshake": { "us": 2963 } } }, "tcp": { "rtt": { "connect": { "us": 523 } }, "port": 443 }, "beat": { "hostname": "rrc102-198819-rrc102-wpar", "name": "rrc102-198819-rrc102-wpar", "version": "6.7.0" }, "@timestamp": "2019-04-02T21:43:50.000Z", "tags": [ "beats\_input\_raw\_event" ], "resolve": { "host": "[cloud1.rationalenterprise.com](http://cloud1.rationalenterprise.com)", "rtt": { "us": 886 }, "ip": "35.229.64.130" }, "event": { "dataset": "uptime" }, "host": { "name": "rrc102-198819-rrc102-wpar" }, "monitor": { "status": "up", "ip": "35.229.64.130", "id": "http@[https://cloud1.rationalenterprise.com/#/core/login](https://cloud1.rationalenterprise.com/#/core/login)", "host": "[cloud1.rationalenterprise.com](http://cloud1.rationalenterprise.com)", "duration": { "us": 310665 }, "scheme": "https", "name": "http", "type": "http" }, "http": { "response": { "status\_code": 200 }, "url": "[https://cloud1.rationalenterprise.com/#/core/login](https://cloud1.rationalenterprise.com/#/core/login)", "rtt": { "total": { "us": 309651 }, "response\_header": { "us": 306043 }, "write\_request": { "us": 67 }, "validate": { "us": 306091 }, "content": { "us": 48 } } } }, "fields": { "tls.certificate\_not\_valid\_after": [ "2019-04-27T23:59:59.000Z" ], "tls.certificate\_not\_valid\_before": [ "2016-01-28T00:00:00.000Z" ], "@timestamp": [ "2019-04-02T21:43:50.000Z" ] }, "highlight": { "beat.hostname": [ "@kibana-highlighted-field@rrc102@/kibana-highlighted-field@-@kibana-highlighted-field@198819@/kibana-highlighted-field@-@kibana-highlighted-field@rrc102@/kibana-highlighted-field@-@kibana-highlighted-field@wpar@/kibana-highlighted-field@" ] }, "sort": [ 1554241430000 ] }" ---
**Author:** ![dov0211](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dov0211/32/36505_2.png) [@dov0211](https://discuss.elastic.co/u/dov0211)\ **Post date:** [April 3, 2019, 6:36pm UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004/4 "2019-04-03T18:36:54Z")
Update: Customer had Dropped all existing heartbeat templates and indices then created a single new 6.7.0 template. When the new index came in from logstash all was resolved. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 3, 2019, 8:47pm UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004/5 "2019-04-03T20:47:37Z")
Just a quick suggestion @frankfoti, it is helpful to wrap code/logs/data in markdown style backticks, or use the `` (code formatting) button to make things easier to read 🙂 ---
**Author:** ![jkambic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkambic/32/53306_2.png) [@jkambic](https://discuss.elastic.co/u/jkambic)\ **Post date:** [April 3, 2019, 8:48pm UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004/6 "2019-04-03T20:48:56Z")
@dov0211 thanks for the summary explaining the solution! ---
**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\ **Post date:** [April 4, 2019, 11:24am UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004/7 "2019-04-04T11:24:54Z")
``` { ``` "\_index": "heartbeat-6.7.0-2019.04.02", "\_type": "doc", "\_id": "uSwC4GkB0iONRnXhJm95", "\_version": 1, "\_score": null, "\_source": { "@version": "1", "tls": { "certificate\_not\_valid\_after": "2019-04-27T23:59:59.000Z", "certificate\_not\_valid\_before": "2016-01-28T00:00:00.000Z", "rtt": { "handshake": { "us": 2963 } } } ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 28, 2019, 11:24am UTC](https://discuss.elastic.co/t/6-6-upgrade-to-6-7-on-elastic-cloud-uptime-data-not-showing/175004/8 "2019-04-28T11:24:57Z")
This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.