[Beats Monitoring] Monitoring data payload has breaking changes in schema from 6.3 to 7.0 #7562
Description
In 6.3.x, the beats_stats field in .monitoring-beats data looks like:
"beats_stats": {
"timestamp": ...
"beat": {
"type": "filebeat",
"version": "6.3.1",
...
},
"metrics": {
"libbeat": {
"config": {
...
},
"output": {
"events": {
...
},
"write": {
...
},
"read": {
...
},
"type": ...
},
"pipeline": {
"clients": ...,
"events": {
...
},
"queue": ...
}
},
"system": {
...
},
"beat": {
...
},
...
}
}
In 7.0/master branch, the beats_stats schema has changed and now looks like:
"beats_stats": {
"timestamp": ...,
"beat": {
"type": "filebeat",
"version": "7.0.0-alpha1",
...
},
"stats": { # WAS: metrics
"libbeat": {
"config": {
...
},
"output": {
"events": {
...
},
"write": {
...
},
"read": {
...
},
"type": ...
},
"pipeline": {
"clients": ...,
"events": {
...
},
"queue": ...
}
},
"system": {
...
},
"beat": {
...
},
...
}
}
(Ellipses added for length)
This is a breaking change for the Monitoring UI, since beats_stats.metrics is used for a lot of info about Beats in the cluster.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Give feedbackNo fields configured for issues without a type.