-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heartbeat event data structure #3406
Comments
For what it's worth, the boolean type for the "up" field is kind of a pain in Kibana. I suggest making it (also) a string. |
how about changing "up" to "status" with values "up", "down" for now? |
@urso That's a good idea to have |
I suggest to combine some fields, for example: Before:
After:
I would say to export either |
I would suggest combining together also rttp related times. A possible option can be: Before:
After:
|
For HTTP, not sure if it makes sense to export both |
I like the idea to have the "common" fields under the We will also need |
+1 on keeping URL. users can pass additional GET parameters right in the URL.
Note, The Or have
This way, there is some overlap between
New event structure:
current available rtt types: |
As The |
Including 'nesting' by protocol, I'd remove the some samples:
|
we can report protocol info either by monitor, or top-level. |
Seems like we are mostly on the same page :-) +1 on per monitor. |
with nesting and moving monitor specific fields, http event will look like:
|
👍 on the proposal above. |
👍 on the above proposal, but I suggest to export the minimal fields by default. For example, I would not export |
In general it looks like the data structure will compress quite well as the only values that change for each event are probably rtt and timestamp. |
This is a first take on changing the event structure to elastic#3406 (comment) * move up to status -> up / down. In the example it is status.type: up? Reason?
This has been implemented in #4091. |
This issue is to discuss the heartbeat event data structure. The current structure (with error) looks as following:
http
tcp
icmp
The text was updated successfully, but these errors were encountered: