-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[logging] Upgrade ECS to 8.0 #113662
[logging] Upgrade ECS to 8.0 #113662
Conversation
Pinging @elastic/kibana-core (Team:Core) |
@elasticmachine merge upstream |
@@ -7,7 +7,7 @@ | |||
*/ | |||
|
|||
/** | |||
* https://www.elastic.co/guide/en/ecs/1.12/ecs-agent.html | |||
* https://www.elastic.co/guide/en/ecs/master/ecs-agent.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you going to upgrade it to 8.0
in the next PR? master
might be out of sync with the definitions in the Kibana repo, so we should prefer a pinned version in the link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah we will need to update this in a follow-up as the 8.0 docs aren't available until FF, so all we have is master
.
As an alternative we could just link now to the 8.0 URLs, which will return a 404 until they are available.
@@ -1,13 +1,13 @@ | |||
// Jest Snapshot v1, https://goo.gl/fbAQLP | |||
|
|||
exports[`\`format()\` correctly formats record. 1`] = `"{\\"ecs\\":{\\"version\\":\\"1.12.0\\"},\\"@timestamp\\":\\"2012-02-01T09:30:22.011-05:00\\",\\"message\\":\\"message-1\\",\\"error\\":{\\"message\\":\\"Some error message\\",\\"type\\":\\"Some error name\\",\\"stack_trace\\":\\"Some error stack\\"},\\"log\\":{\\"level\\":\\"FATAL\\",\\"logger\\":\\"context-1\\"},\\"process\\":{\\"pid\\":5355}}"`; | |||
exports[`\`format()\` correctly formats record. 1`] = `"{\\"ecs\\":{\\"version\\":\\"8.0.0\\"},\\"@timestamp\\":\\"2012-02-01T09:30:22.011-05:00\\",\\"message\\":\\"message-1\\",\\"error\\":{\\"message\\":\\"Some error message\\",\\"type\\":\\"Some error name\\",\\"stack_trace\\":\\"Some error stack\\"},\\"log\\":{\\"level\\":\\"FATAL\\",\\"logger\\":\\"context-1\\"},\\"process\\":{\\"pid\\":5355}}"`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind updating the test suite with ecs.version
assertion against a string to avoid test flakiness?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I already asserted against the string itself in the next test, however I went ahead and updated these snapshots so they don't contain a version either. That way there's only one test that needs to be changed when the ECS version is bumped.
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @lukeelmers |
Closes #112175
Summary
I'm splitting the work outlined in #112175 into two parts:
Part 1 (merged in [logging] Upgrade ECS to 1.12 #113583): Upgrade ECS types to 1.12.0. Will be backported to 7.x to coincide with the 7.16 stack release.[1] Starting in 8.0, ECS will be aligning their versioning with stack releases, hence the jump from 1.12 to 8.0
Testing
CHANGELOG.next.md
on ECS's currentmaster
branch.I'm going to skip adding a breaking changes note here, as I think this will already be covered more broadly by #112305