Byte size in is bigger than real traffic packages in Network Explore

Elastic Security
1

elasticsearch-8.6.1
kibana-8.6.1
logstash-8.6.1

I install packetbeat in the VM which install elastic stack. When I try to use Security - Explore - Network in Kibana, I find that the traffice Bytes account is much more than real network traffice.

explore
explore3674×1170 297 KB

Then I try to check logs in Discover. I find for each source.port there is a log and there is a bytes_in and bytes_out. I don't know if "Security - Explore - Network" add all the bytes_in or bytes_out in each line of the log so make the value so large?

packetbeet2
packetbeet23710×1060 305 KB

2

Hi, Wishes, and welcome to our community!

The Source and Destination table on the Network page does a sum aggregation on destination.bytes or source.bytes to calculate "Byten in" and "Bytes out". So it adds destination.bytes or source.bytes in each log line to calculate the total value.
I simplified the query (for a fixed time range), making it easier to read and understand how the data is calculated.

GET packetbeat-*/_search
{
  "aggregations": {
    "source": {
      "terms": {
        "field": "source.ip",
        "size": 10,
        "order": {
          "bytes_in": "desc"
        }
      },
      "aggs": {
        "bytes_in": {
          "sum": {
            "field": "destination.bytes"
          }
        },
        "bytes_out": {
          "sum": {
            "field": "source.bytes"
          }
        }
      }
    }
  },
  "query": {
    "bool": {
      "filter": [
        {
          "range": {
            "@timestamp": {
              "gte": "2023-03-22T13:34:17.938Z",
              "lte": "2023-03-22T13:44:17.938Z",
              "format": "strict_date_optional_time"
            }
          }
        }
      ]
    }
  },
  "_source": false,
  "size": 0
}

Please; let me know if you need any further information.

3

Hi Machadoum,

Thanks for your feedback. I know why the Bytes_in and Bytes_out in Security - Explore- Network is so large now.
But I think the result in Security - Explore- Network is not true. Will Elastic change the way to count the "Byte In" and "Byte Out"? I think it's not good to do a sum aggregation on destination.bytes or source.bytes to calculate "Byten in" and "Bytes out"

4

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