-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Finish ECS migration for Packetbeat #10193
Conversation
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.
New content of this PR LGTM.
The comment about scale
for ecs-migration.yml shouldn't be considered a blocker. It's a tweak we may put in place separately to generate better migration docs.
comment: > | ||
Units changed from usec to nsec. Don't add an alias until all of Packetbeat | ||
stops using this field. | ||
comment: The units changed so no alias was added. |
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.
@ruflin I think it would be worth adding (yet another) field for entries in this file, to indicate scale difference on fields that can't be directly aliased but are still gone nonetheless. WDYT?
Most of the fields I've migrated to event.duration
were ms to nano, but there was at least one which was micro to nano.
So we could have
- from: responsetime
to: event.duration
alias: false
scale: 1000
comment: > comment: The units changed so no alias was added.
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 added the scale
field for responsetime
.
Based on my suggestion over on Andrew's PR: elastic#10193 (comment)
0f5b3f4
to
d2cf852
Compare
@andrewkroh Ok, good for me. Ping me when this is rebased over the merged pgsql, so I can approve quickly. |
d2cf852
to
c5a96a1
Compare
Rebased. The pgsql commits are removed. |
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.
Went through everything again, and LGTM.
If I understand correctly, method
stays there for non-HTTP protocols that still have a "method", and path
stays for paths that aren't URLs?
Since this is a cleanup PR after all the other ones, what's the changelog customs? Add a mention of this PR on each changelog entry? Or are the current entries enough? |
- Add aliases - Clean up config files - Remove unused fields from fields.common.yml - Remove time_zone from dashboards - Update navigation links on dashboards to include all dashboards - Add DNS / TLS to overview dashboard to highlight the capabilities - Update fields used in the documentation - Move RPC fields to NFS from Mongo (they were in the wrong package) Part of elastic#7968
c5a96a1
to
6707e86
Compare
@webmat I have consolidated the changelog entries into one that points to the overall issue. The issue has links to each PR. |
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.
Typo, then we're good
There are a few protocols populating |
Agreed on always filling |
NOTE: This is based on some other open PRs and will be rebased after they merge. Please only review the last commit.
This should finish out the field updates for Packetbeat.
Part of #7968