Start Packetbeat
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Before 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.
sudo chown root packetbeat.yml
sudo ./packetbeat -e
- You’ll be running Packetbeat as root, so you need to change ownership of the configuration file, or run Packetbeat with
--strict.perms=falsespecified. See Config File Ownership and Permissions.
sudo chown root packetbeat.yml
sudo ./packetbeat -e
- You’ll be running Packetbeat as root, so you need to change ownership of the configuration file, or run Packetbeat with
--strict.perms=falsespecified. See Config File Ownership and Permissions.
PS C:\Program Files\packetbeat> Start-Service packetbeat
By default Windows log files are stored in C:\Program Files\Packetbeat-Data\logs.
In versions before 9.0.6, the default location for Windows log files was C:\ProgramData\packetbeat\logs.