package/network_traffic/tls: fix mapping for tls.detailed.server_certificate_chain #2517
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.
What does this PR do?
This brings the mapping for server_certificate_chain into agreement with the packetbeat code and mapping, fixing #2499.
Checklist
changelog.yml
file.Author's Checklist
The mapping for tls.server.certificate_chain in ECS disagrees with this change. I believe this is wrong based on the information required to describe a cert and that the packetbeat code marshals to atls.server.certificate_chain is presumably intended to be filled with a string representation of the chain elements.[]common.MapStr
.How to test this PR locally
elastic-package test system --data-streams tls
in the network_traffic package.Related issues
Screenshots
N/A