-
Notifications
You must be signed in to change notification settings - Fork 538
model: ECS for 6.x #1609
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
model: ECS for 6.x #1609
Changes from all commits
a6af765
701050d
ceeffdb
99c19c7
75a4085
4c40f12
bb6dd7b
e122d1d
3a7330a
4c4f153
4702718
1b24cdd
5f5110f
bbd74c5
1623c46
a1691ff
db16a71
8430094
3ce04c0
bd15cba
eb87599
c72fbd1
fe3f320
444fbf8
81303c6
2948e80
8e8880b
b444e4b
6301a52
9526e03
7c83ca4
da90de7
5ebf75e
629356d
c45b98d
2a8fecf
1004b8f
a548225
cd12363
304bcc7
fb54f5e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,140 @@ | ||
| # The ECS migration file contains the information about all the fields which are migrated to ECS in 7.0. | ||
| # The goal of the file is to potentially have scripts on top of this information to convert visualisations and templates | ||
| # based on this information in an automated way and to keep track of all changes which were applied. | ||
| # | ||
| # The format of the file is as following: | ||
| # | ||
| # - from: source-field-in-6.x | ||
| # to: target-filed-in-ECS | ||
| # # Alias field is useful for fields where there is a 1-1 mapping from old to new | ||
| # alias: true-if-alias-is-required-in-6x (default is true) | ||
| # # Copy to is useful for fields where multiple fields map to the same ECS field | ||
| # copy_to: true-if-field-should-be-copied-to-target-in-6x (default is false) | ||
|
|
||
| - from: beat.hostname | ||
| to: observer.hostname | ||
|
|
||
| - from: beat.name | ||
| to: observer.type | ||
|
|
||
| - from: beat.version | ||
| to: observer.version | ||
|
|
||
| - from: context.service.agent.name | ||
| to: agent.name | ||
|
|
||
| - from: context.service.agent.version | ||
| to: agent.version | ||
|
|
||
| - from: context.system.architecture | ||
| to: host.architecture | ||
|
|
||
| - from: context.system.hostname | ||
| to: host.hostname | ||
webmat marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| - from: context.system.ip | ||
| to: host.ip | ||
|
|
||
| - from: context.system.platform | ||
| to: host.os.platform | ||
|
|
||
| - from: context.request.method | ||
| to: http.request.method | ||
|
|
||
| - from: context.request.http_version | ||
| to: http.version | ||
simitt marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| - from: context.process.pid | ||
| to: process.pid | ||
|
|
||
| - from: context.process.ppid | ||
| to: process.ppid | ||
|
|
||
| - from: context.process.title | ||
| to: process.title | ||
graphaelli marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| # not in ECS | ||
| - from: context.service.environment | ||
| to: service.environment | ||
|
|
||
| # not in ECS | ||
| - from: context.service.framework.name | ||
| to: service.framework.name | ||
|
|
||
| # not in ECS | ||
| - from: context.service.framework.version | ||
ruflin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| to: service.framework.version | ||
|
|
||
| # not in ECS | ||
| - from: context.service.language.name | ||
| to: service.language.name | ||
|
|
||
| # not in ECS | ||
| - from: context.service.language.version | ||
| to: service.language.version | ||
|
|
||
| - from: context.service.name | ||
| to: service.name | ||
|
|
||
| # not in ECS | ||
| - from: context.service.runtime.name | ||
| to: service.runtime.name | ||
|
|
||
| # not in ECS | ||
| - from: context.service.runtime.version | ||
| to: service.runtime.version | ||
|
|
||
| - from: context.service.version | ||
| to: service.version | ||
|
|
||
| - from: context.request.url.full | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @webmat I wonder if we should allow to nest There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If there's only one URL in the event, I don't see a reason to do move it around. We need to control in how many places things can be nested. Each time we do this, we're growing the amounts of expected places that fields can be found in ECS, which is contrary to ECS' goal of making things easier to find across data sources. |
||
| to: url.full | ||
|
|
||
| - from: context.request.url.hash | ||
| to: url.fragment | ||
|
|
||
| - from: context.request.url.hostname | ||
| to: url.domain | ||
|
|
||
| - from: context.request.url.pathname | ||
| to: url.path | ||
|
|
||
| - from: context.request.url.port | ||
| to: url.port | ||
| alias: false | ||
| copy_to: true | ||
|
|
||
| - from: context.request.url.raw | ||
| to: url.original | ||
simitt marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| - from: context.request.url.search | ||
| to: url.query | ||
|
|
||
| - from: context.request.url.protocol | ||
| to: url.scheme | ||
| alias: false | ||
| copy_to: true | ||
|
|
||
| - from: context.response.finished | ||
| to: http.response.finished | ||
|
|
||
| - from: context.response.status_code | ||
| to: http.response.status_code | ||
|
|
||
| - from: context.user.email | ||
| to: user.email | ||
|
|
||
| - from: context.user.id | ||
| to: user.id | ||
|
|
||
| - from: context.user.username | ||
| to: user.name | ||
|
|
||
| - from: context.user.ip | ||
| to: client.ip | ||
graphaelli marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| - from: context.user.user-agent | ||
| to: user_agent.original.text | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I guess we're hitting a corner case here. The field (in terms of setting an alias) is moving to But the usage side, if APM intends to use this as "what field does the query target", then yeah it's now cc @ruflin
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. you can alias to a multi-field but not back from a multi-field (marked as a non-reversible alias) |
||
|
|
||
| - from: listening | ||
| to: observer.listening | ||
graphaelli marked this conversation as resolved.
Show resolved
Hide resolved
|
||
Uh oh!
There was an error while loading. Please reload this page.