Historically when heartbeat encountered an error it would fail fast and log an error, in some cases even exit completely. As we evolve our GUI-centricity and work toward a service this mode of operation becomes less desirable. All errors should be obvious in the Uptime UI unless there is no way to communicate back to ES. This means indexing a document whenever an error happens.

This meta issue serves to track work / issues toward this goal.

• [Heartbeat] Synthetics checks do not send summary event when node exits early #28770
• [Heartbeat] ICMP checks fail on systems without ipv6, even if they are only checking ICMPv4 #29346
• [Heartbeat] Defer monitor / ICMP errors to monitor runtime / ES #29413
  • Validate that running on prem with ELASTIC_SYNTHETICS_CAPABLE=FALSE produces an error in the Kibana UI
  • Verify that if script params are invalid, this should not be savable
• Inline monitor syntax errors should send errors to ES #29897
  • If an invalid param is set on Synthetics Agrs this should produce an error in the Kibana UI
• [META] Suite Discovery / Monitor Management Integration uptime#432
• When journey/end is not reported - Heartbeat: report summary event when synthetics doesn't emit end event #30729