The Visualisations for Inbound and Outbound traffic in this OOTB dashboard utilises data from source.bytes and destination.bytes fields.
The integration's ingest pipeline is currently only parsing and populating these fields for TCP Logs from Classic ELB & NLB.
It seems the values parsed from ALB logs to populate http.request.body.bytes and http.response.body.bytes fields should also be used to populate source.bytes and destination.bytes fields to address this issue.
The Visualisations for Inbound and Outbound traffic in this OOTB dashboard utilises data from
source.bytesanddestination.bytesfields.The integration's ingest pipeline is currently only parsing and populating these fields for TCP Logs from Classic ELB & NLB.
It seems the values parsed from ALB logs to populate
http.request.body.bytesandhttp.response.body.bytesfields should also be used to populatesource.bytesanddestination.bytesfields to address this issue.