Uptime app 7.9.1 - "Internal server error"

Elastic Observability Synthetics
6

Hi @jkambic,

  • Ran: GET heartbeat-7.9.1/_mapping/field/observer.geo.name

  • Response:

    {
    "error" : {
    "root_cause" : [
    {
    "type" : "index_not_found_exception",
    "reason" : "no such index [heartbeat-7.9.1]",
    "resource.type" : "index_or_alias",
    "resource.id" : "heartbeat-7.9.1",
    "index_uuid" : "na",
    "index" : "heartbeat-7.9.1"
    }
    ],
    "type" : "index_not_found_exception",
    "reason" : "no such index [heartbeat-7.9.1]",
    "resource.type" : "index_or_alias",
    "resource.id" : "heartbeat-7.9.1",
    "index_uuid" : "na",
    "index" : "heartbeat-7.9.1"
    },
    "status" : 404
    }

  • Stopped Heartbeat

  • Removed index heartbeat-7.9.1

  • Removed Legacy index template heartbeat-7.9.1

  • Ran GET /_cat/indices. Found the other beats indexes, but nothing mentioning heartbeat

  • Confirmed Uptime can't find any index to read from

    Uptime-empty
    Uptime-empty1765×584 48.8 KB

  • Ran .\heartbeat.exe setup to create index and template (no errors)

  • Started heartbeat service (no errors)

  • Ran: GET /_cat/indices

  • Response:

green open heartbeat-7.9.1 iF4pc8ySSza5XtM_z40yzg 1 0 19 0 119.8kb 119.8kb

  • Confirmed index and index template added for heartbeat-7.9.1
  • Ran: GET heartbeat-7.9.1/_mapping/field/observer.geo.name
  • Response:
    {
    "heartbeat-7.9.1" : {
    "mappings" : { }
    }
    }

From this point the issue has been reproduced. Uptime is showing again the "Internal server error". Is this Heartbeat version not mapping correctly when running the setup?

1 Like