Metricbeat host namespace causes mapping conflict when used with Logstash
#7050
Comments
tsg
added a commit
to tsg/beats
that referenced
this issue
May 9, 2018
As a solution for elastic#7050, we adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes elastic#7050.
ruflin
pushed a commit
that referenced
this issue
May 10, 2018
As a solution for #7050, we're adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes #7050.
tsg
added a commit
to tsg/beats
that referenced
this issue
May 10, 2018
As a solution for elastic#7050, we're adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes elastic#7050. (cherry picked from commit 15d9539)
monicasarbu
pushed a commit
that referenced
this issue
May 10, 2018
* Add host.name in the events (#7051) As a solution for #7050, we're adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes #7050. (cherry picked from commit 15d9539) * changelog cleanup
stevea78
pushed a commit
to stevea78/beats
that referenced
this issue
May 20, 2018
As a solution for elastic#7050, we're adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes elastic#7050.
stevea78
pushed a commit
to stevea78/beats
that referenced
this issue
May 20, 2018
As a solution for elastic#7050, we're adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes elastic#7050.
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
…#7068) * Add host.name in the events (elastic#7051) As a solution for elastic#7050, we're adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes elastic#7050. (cherry picked from commit 1889f9c) * changelog cleanup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is what's happening:
add_host_metadataprocessor creates ahostobject. The new processor is disabled by default, but the fields are present in the Beats templates.host(string) if host is not found in the original object. Code is herehostsent from Logstash to Elasticsearch is a string. This conflicts with the object mapping that we have in the Metricbeat template.The result of the above is that a stock MB -> LS -> ES pipeline doesn't work :(
The text was updated successfully, but these errors were encountered: