Monitor.id duplicated on service restart

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?

@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.

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