Add ip and status to heartbeat dashboard table (#9022)

The heartbeat dashboard table currently doesn't include these fields by default. These fields are useful for two reasons: 1. A given monitor.id often runs against separate IPs which may have different downtime results 2. Viewing the latest status for a given id/status tuple is a common use case. It answers the question: "what's down?". Fixes #8972
elastic · Nov 26, 2018 · b3de5f6 · b3de5f6
1 parent 96c924a
commit b3de5f6
Show file tree

Hide file tree

Showing 2 changed files with 725 additions and 681 deletions.
diff --git a/CHANGELOG.asciidoc b/CHANGELOG.asciidoc
@@ -324,6 +324,7 @@ https://github.com/elastic/beats/compare/v6.4.0...v6.5.0[View commits]
 - Added autodiscovery support {pull}8415[8415]
 - Added support for extra TLS/x509 metadata. {pull}7944[7944]
 - Added stats and state metrics for number of monitors and endpoints started. {pull}8621[8621]
+- Add last monitor status to dashboard table. Further break out monitors in dashboard table by monitor.ip. {pull}9022[9022]
 
 *Journalbeat*