Start Packetbeat
editStart Packetbeat
editBefore starting Packetbeat:
- Follow the steps in Quick start: installation and configuration to install, configure, and set up the Packetbeat environment.
- Make sure Kibana and Elasticsearch are running.
-
Make sure the user specified in
packetbeat.ymlis authorized to publish events.
To start Packetbeat, run:
sudo service packetbeat start
If you use an init.d script to start Packetbeat, you can’t specify command
line flags (see Command reference). To specify flags, start Packetbeat in
the foreground.
Also see Packetbeat and systemd.
sudo service packetbeat start
If you use an init.d script to start Packetbeat, you can’t specify command
line flags (see Command reference). To specify flags, start Packetbeat in
the foreground.
Also see Packetbeat and systemd.
|
You’ll be running Packetbeat as root, so you need to change ownership
of the configuration file, or run Packetbeat with |
To have launchd start elastic/tap/packetbeat and then restart it at login,
run:
brew services start elastic/tap/packetbeat-full
To run Packetbeat in the foreground instead of running it as a background service, run:
|
You’ll be running Packetbeat as root, so you need to change ownership
of the configuration file, or run Packetbeat with |
|
You’ll be running Packetbeat as root, so you need to change ownership
of the configuration file, or run Packetbeat with |
PS C:\Program Files\packetbeat> Start-Service packetbeat
By default, Windows log files are stored in C:\ProgramData\packetbeat\Logs.