[Libbeat] Fix docker autodiscovery to follow ECS#10758
Closed
ruflin wants to merge 3 commits intoelastic:masterfrom
Closed
[Libbeat] Fix docker autodiscovery to follow ECS#10758ruflin wants to merge 3 commits intoelastic:masterfrom
ruflin wants to merge 3 commits intoelastic:masterfrom
Conversation
ruflin
commented
Feb 15, 2019
| "name": container.Image, | ||
| }, | ||
| // TODO: Do we need some dedotting here? | ||
| "labels": labelMap, |
Contributor
Author
There was a problem hiding this comment.
@kaiyan-sheng I remember you discussed this with Carlos. What is the conclusion of dedotting of labels in 7 in Docker?
Contributor
There was a problem hiding this comment.
We don't need dedotting here for autodiscover because the autodiscover events are for internal use, will not store into ES. @jsoriano Please correct me if I'm wrong. Thanks!
ruflin
commented
Feb 15, 2019
| 'templates': ''' | ||
| - condition: | ||
| equals.docker.container.image: memcached:latest | ||
| equals.container.image: memcached:latest |
Contributor
Author
There was a problem hiding this comment.
For 6.7, let's make sure we check both.
This was referenced Feb 18, 2019
jsoriano
added a commit
that referenced
this pull request
Feb 25, 2019
Fields injected by docker autodiscover provider were being placed in alias fields introduced for ECS, change them to the new location and add selectors accordingly. This PR includes #10862 and #10758 As a summary: * Autodiscover selectors using ECS structure are added to autodiscover events, old selectors are kept for backwards compatibility * Autodiscover generated metadata follows ECS * Dedotting of labels is added, enabled by default, will be backported for 6.7, but disabled `docker.containers.labels` is not migrated, as it wasn't for `add_docker_metadata` (see #9412) Fixes #10757 Co-Authored-By: kaiyan-sheng <kaiyan.sheng@elastic.co> Co-Authored-By: Nicolas Ruflin <spam@ruflin.com>
Member
|
Merged as part of #10898 |
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Feb 25, 2019
Fields injected by docker autodiscover provider were being placed in alias fields introduced for ECS, change them to the new location and add selectors accordingly. This PR includes elastic#10862 and elastic#10758 As a summary: * Autodiscover selectors using ECS structure are added to autodiscover events, old selectors are kept for backwards compatibility * Autodiscover generated metadata follows ECS * Dedotting of labels is added, enabled by default, will be backported for 6.7, but disabled `docker.containers.labels` is not migrated, as it wasn't for `add_docker_metadata` (see elastic#9412) Fixes elastic#10757 Co-Authored-By: kaiyan-sheng <kaiyan.sheng@elastic.co> Co-Authored-By: Nicolas Ruflin <spam@ruflin.com> (cherry picked from commit 1bf8087)
jsoriano
added a commit
that referenced
this pull request
Feb 27, 2019
Fields injected by docker autodiscover provider were being placed in alias fields introduced for ECS, change them to the new location and add selectors accordingly. This PR includes #10862 and #10758 As a summary: * Autodiscover selectors using ECS structure are added to autodiscover events, old selectors are kept for backwards compatibility * Autodiscover generated metadata follows ECS * Dedotting of labels is added, enabled by default, will be backported for 6.7, but disabled `docker.containers.labels` is not migrated, as it wasn't for `add_docker_metadata` (see #9412) Fixes #10757 (cherry picked from commit 1bf8087) Co-Authored-By: kaiyan-sheng <kaiyan.sheng@elastic.co> Co-Authored-By: Nicolas Ruflin <spam@ruflin.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
See #10757