# Monitor.id duplicated on service restart
**URL:** https://discuss.elastic.co/t/monitor-id-duplicated-on-service-restart/176974
**Category:** Beats
**Tags:** heartbeat
**Created:** [April 15, 2019, 9:02pm UTC](https://discuss.elastic.co/t/monitor-id-duplicated-on-service-restart/176974 "2019-04-15T21:02:19Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@RayS](https://discuss.elastic.co/u/RayS)
#### Post date: [April 15, 2019, 9:02pm UTC](https://discuss.elastic.co/t/monitor-id-duplicated-on-service-restart/176974/1 "2019-04-15T21:02:20Z")
Running version 7 of heartbeat. If I restart the heartbeat-elastic server I end up with duplicate monitor.id entries on the Heartbeat HTTP Monitoring Dashboard. Two questions:
1. Is this normal and if so what's the logic behind it?
2. Is there a way to give the monitor.id a "friendly" name?
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [April 22, 2019, 5:10pm UTC](https://discuss.elastic.co/t/monitor-id-duplicated-on-service-restart/176974/2 "2019-04-22T17:10:32Z")
@RayS in Heartbeat 7 we generate stable IDs by hashing the individual monitor config. If you change any parameters for the monitor it will change the ID as a result. For this reason we recommend setting the `id` parameter explicitly in Heartbeat 7.
Does that explain what you're seeing? If you're seeing the ID change without accompanying config changes that would be a bug.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 20, 2019, 5:10pm UTC](https://discuss.elastic.co/t/monitor-id-duplicated-on-service-restart/176974/3 "2019-05-20T17:10:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.