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.
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
Switch to base 16 for TLS serial number in packetbeat in line with ECS changes #41542
base: main
Are you sure you want to change the base?
Switch to base 16 for TLS serial number in packetbeat in line with ECS changes #41542
Changes from 2 commits
3b00e70
1698a96
778ff3b
95be01e
9bf37be
6efedf2
a53fca0
75da1cf
b45aafd
fec9267
873800e
47309c2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 21 in packetbeat/protos/tls/parse.go
GitHub Actions / lint (linux)
Check failure on line 273 in packetbeat/protos/tls/parse.go
GitHub Actions / lint (linux)
Check failure on line 303 in packetbeat/protos/tls/parse.go
GitHub Actions / lint (linux)
Check failure on line 353 in packetbeat/protos/tls/parse.go
GitHub Actions / lint (linux)
Check failure on line 356 in packetbeat/protos/tls/parse.go
GitHub Actions / lint (linux)
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.
Note that all of the fields under
tls.detailed.*
are not part of ECS. I cannot find any definition of this field within elastic/beats that needs updated, but it is defined at https://github.com/elastic/integrations/blob/7d7358618583e3d34e83e645d8bb7c83eda58253/packages/network_traffic/data_stream/tls/fields/protocol.yml#L210-L212 so that side will also need an update.I recommend updating that definition at the same time in which you update the ECS version12 for the network_traffic integration (after we have an ECS release).
Footnotes
https://github.com/elastic/integrations/blob/7d7358618583e3d34e83e645d8bb7c83eda58253/packages/network_traffic/_dev/build/build.yml ↩
https://github.com/search?q=repo%3Aelastic%2Fintegrations+path%3A%2F%5Epackages%5C%2Fnetwork_traffic%5C%2Fdata_stream%5C%2F.*default%5C.yml%2F+%2Fecs%5C.version%2F&type=code ↩