I have the latest version of elastic cloud deployment (v7.15.0).
I have 3 instances of heartbeat v7.15.0 running on 3 separate machines pinging same websites and all are sending to same index. Their heartbeat.yml files are identical.
I'm receiving data from heartbeat and can discover and can create visualizations/dashboards with that data. But when I go to Observability > Uptime > Monitors I'm greeted with "An internal server error occurred" message!
I tried
Stopping all HB instances
Deleting the Index
Confirming that the Uptime page shows warning about Index being empty
@Tadija to be clear, we haven't started work on the fix. I would like to see it in 7.16.0, but that may not happen.
This issue should be fixable by following those steps. If it didn't work the likely cause was that you did not shut down all heartbeats before deleting indices and aliases. If one heartbeat is running it will mess up the mappings again.
Also, I've removed the solution mark since proposed steps did not fix the issue. I would be happy with some workaround. I followed the linked steps a couple of times, unfortunately the y do not help.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.