Adding default templates for Metricbeat ECS data #81744
Conversation
elasticmachine
added
the
Team:Data Management
|
Pinging @elastic/es-data-management (Team:Data Management) |
|
@elasticmachine update branch |
|
@elasticmachine run elasticsearch-ci/part-2 |
| @@ -0,0 +1,2198 @@ | |||
| { | |||
| "index_patterns": [".monitoring-beats-${xpack.stack.monitoring.template.version}-*"], | |||
There was a problem hiding this comment.
This is the same pattern as https://github.com/elastic/elasticsearch/blob/master/x-pack/plugin/core/src/main/resources/monitoring-es.json#L2 - are we planning to introduce a new variable to set the mb version to 10?
There was a problem hiding this comment.
Currently the xpack.stack.monitoring.template.version is set to version 8 for the metricbeat indices. We talked it over a bit more and agreed that 8 was indeed the more appropriate version number to put here. The monitoring-es.json file uses the xpack.monitoring.template.version property (doesn't contain stack)
There was a problem hiding this comment.
ah... xpack.monitoring.template.version vs xpack.stack.monitoring.template.version - I missed the distinction. Thanks!
Co-authored-by: Mat Schaffer <mat@schaffer.me>
|
@elasticmachine update branch |
This PR adds four new templates that are automatically installed from the Monitoring plugin. In 8.x, Metricbeat will be writing its data in ECS compliant format, even when used with xpack mode enabled (stack monitoring). In order to continue to support the legacy data format, new mappings have been created with the new ECS fields for indexing data, and alias fields for the legacy format which point to the corresponding ECS fields. Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Mat Schaffer <mat@schaffer.me>
This PR adds four new templates that are automatically installed from the Monitoring plugin. In 8.x, Metricbeat will be writing its data in ECS compliant format, even when used with xpack mode enabled (stack monitoring). In order to continue to support the legacy data format, new mappings have been created with the new ECS fields for indexing data, and alias fields for the legacy format which point to the corresponding ECS fields. Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Mat Schaffer <mat@schaffer.me>
This PR adds four new templates that are automatically installed from the Monitoring plugin.
In 8.x, Metricbeat will be writing its data in ECS compliant format, even when used with xpack mode enabled (stack monitoring). In order to continue to support the legacy data format, new mappings have been created with the new ECS fields for indexing data, and alias fields for the legacy format which point to the corresponding ECS fields.
New templates added:
.monitoring-beats-mbmatching on.monitoring-beats-8-*defined inmonitoring-beats-mb.json.monitoring-es-mbmatching on.monitoring-es-8-*defined inmonitoring-es-mb.json.monitoring-kibana-mbmatching on.monitoring-kibana-8-*defined inmonitoring-kibana-mb.json.monitoring-logstash-mbmatching on.monitoring-logstash-8-*defined inmonitoring-logstash-mb.jsonAll templates are being created with internal version
8000099