Integrations
Packetbeat

Packetbeat Configuration Example

Ship Network Data with Packetbeat

Packetbeat is a network package analyser used to capture network traffic. It can be used to extract useful fields of information from network transactions before shipping them to one or more destinations, including Logstash. This is useful for troubleshooting and detecting performance hits.

Logs

Install Integration

Please click on the Install Integration button to configure your stack for this source.

Install

To get started first follow the steps below:

Older versions can be found here: packetbeat 7 (opens in a new tab), packetbeat 6 (opens in a new tab), packetbeat 5 (opens in a new tab)

Locate the configuration file

/etc/packetbeat/packetbeat.yml

Configure Packetbeat

Packetbeat needs to be configured to select the network interface from which to capture the traffic.

On Windows, you must also download and install a packet sniffing library, such as Npcap (opens in a new tab), that implements the libpcap interfaces.

Once installed you can then run the following command to list the available network interfaces:

PS C:\Program Files\Packetbeat> .\packetbeat.exe devices
 
0: \Device\NPF_{113535AD-934A-452E-8D5F-3004797DE286} (Intel(R) PRO/1000 MT Desktop Adapter)

On Linux: Packetbeat supports capturing all messages sent or received by the server on which Packetbeat is installed. For this, use any as the device:

packetbeat.interfaces.device: any

On OS X, capturing from the any device does not work. You would typically use either lo0 or en0 depending on which traffic you want to capture.

In this example, there is only one network card, with the index 0, installed on the system. If there are multiple network cards, remember the index of the device you want to use for capturing the traffic.

Modify the device line to point to the index of the device:

packetbeat.interfaces.device: 0

There's also a full example configuration file called packetbeat.full.yml that shows all the possible options.

Configure protocols

In the protocols section, configure the ports on which Packetbeat can find each protocol. If you use any non-standard ports, add them here. Otherwise, the default values should do just fine.

packetbeat.protocols.dns:
  ports: [53]
    
  include_authorities: true
  include_additionals: true
    
packetbeat.protocols.http:
  ports: [80, 8080, 8081, 5000, 8002]
    
packetbeat.protocols.memcache:
  ports: [11211]
 
packetbeat.protocols.mysql:
  ports: [3306]
 
packetbeat.protocols.pgsql:
  ports: [5432]
 
packetbeat.protocols.redis:
  ports: [6379]
 
packetbeat.protocols.thrift:
  ports: [9090]
 
packetbeat.protocols.mongodb:
  ports: [27017]
    
packetbeat.protocols.cassandra:
  ports: [9042]

Configure Output

We will be shipping to Logstash so that we have the option to run filters before the data is indexed.

Comment out the elasticsearch output block.

## Comment out elasticsearch output
#output.elasticsearch:
#  hosts: ["localhost:9200"]
 
# ================================== Outputs ===================================
# ------------------------------ Logstash Output -------------------------------
output.logstash:
hosts: ["@logstash.host:@logstash.sslPort"]
loadbalance: true
ssl.enabled: true

Validate Configuration

In the directory where Filebeat is installed, run the following command to validate the installation:
.\@beatname.exe test config -c @beatname.yml

If the yml file is invalid, @beatname will print a description of the error. For example, if the output.logstash section was missing, @beatname would print no outputs are defined, please define one under the output section

Start Packetbeat

Ok, time to start ingesting data!

sudo service packetbeat start

How to diagnose no data in Stack

If you don't see data appearing in your stack after following this integration, take a look at the troubleshooting guide for steps to diagnose and resolve the problem or contact our support team and we'll be happy to assist.

OssecPalo Alto Networks