chore: add full support for NLB log #44109
Open
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.
Description
Adds full field support for NLB log fields. The table below summarizes NLB field and OTel attribute it ends up (extracted from the updated documentation),
aws.elb.connection_timeaws.elb.tls_handshake_timeaws.elb.incoming_tls_alertaws.elb.chosen_cert_arnaws.elb.chosen_cert_serialaws.elb.tls_named_groupaws.elb.alpn_fe_protocolaws.elb.alpn_be_protocolaws.elb.alpn_client_preference_listaws.elb.tls_connection_creation_timeLink to tracking issue
Fixes #43757
Testing
Unit tests already covered field parsing. But I have added both samples from official AWS NLB documentation at https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-access-logs.html#access-log-entry-format
Documentation
Documentation updated with the new attributes