Add ip and status to heartbeat dashboard table #9022
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 elastic#8972
andrewvc
force-pushed
the
add-status-ip-dash
branch
from
e0f2ef3
to
2780953
Compare
|
jenkins, retest this please |
andrewvc
added
the
Team:obs-ds-hosted-services
andrewvc
added a commit
to andrewvc/beats
that referenced
this pull request
Nov 26, 2018
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 elastic#8972 (cherry picked from commit b3de5f6)
andrewvc
added a commit
that referenced
this pull request
Nov 27, 2018
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 (cherry picked from commit b3de5f6)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The heartbeat dashboard table currently doesn't include these fields by default.
These fields are useful for two reasons:
Fixes #8972