Source.bytes not showing up as a field in elb fileset for aws

I am trying to use the aws module for filebeat. My goal is to recreate the ELB Inbound Traffic [Filebeat AWS] visualization. It does not work by default. I've added an s3 bucket for collecting elb logs and an s3 bucket notification that is connected to an sqs queue. This queue is used as an input in the aws.yml like so

    enabled: true

    # AWS SQS queue url
    var.queue_url: ${ELB_SQS}

When I try to add a data panel to sum the source.bytes field the selector does not show the field. Nor does the field exist when I look at the records from my ellb logs. Here is a screenshot

I would love it if someone could help me with this. I've also attached my filebeat configuration for reference too.

  path: ${path.config}/modules.d/*.yml
  reload.enabled: false
  index.number_of_shards: 1 "host"
setup.kibana.protocol: "https"
setup.kibana.username: "user"
setup.kibana.password: password
setup.dashboards.enabled: true ${path.config}/kibana
setup.ilm.enabled: false
logging.level: debug
  hosts: ["host"]
  protocol: "https"
  username: "user"
  password: password
  bulk_max_size: 3200
  worker: 16
  - index: "cloudtrail-%{[agent.version]}-%{+yyyy.MM.dd}"
      event.dataset: "aws.cloudtrail"
  - index: "elb-%{[agent.version]}-%{+yyyy.MM.dd}"
      event.dataset: "aws.elb"
  - index: "vpc-%{[agent.version]}-%{+yyyy.MM.dd}"
      event.dataset: "aws.vpc"
  - add_fields:
      target: target
        environment: ${ENV}

Hi @EvanGertis,

What kind of load balancers are you collecting logs from? I think that source.bytes is only available for TCP load balancers. For HTTP load balancers you can use http.request.body.bytes/http.response.body.bytes.

For this reason is also possible that the Inbound traffic visualization only works for TCP lbs.

1 Like

Thank you I'm using an HTTP loadbalancer actually.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.