The DEB and RPM packages include a service unit for Linux systems with systemd. On these systems, you can manage Packetbeat by using the usual systemd commands.
systemctl to start or stop Packetbeat:
systemctl start packetbeat
systemctl stop packetbeat
By default, the Packetbeat service starts automatically when the system boots. To enable or disable auto start use:
systemctl enable packetbeat
systemctl disable packetbeat
To get the service status, use
systemctl status packetbeat
Logs are stored by default in journald. To view the Logs, use
journalctl -u packetbeat.service
The unit file included in the packages sets the
-e flag by default.
This flag makes Packetbeat log to stderr and disables other log outputs.
Systemd stores all output sent to stderr in journald.
Customize systemd unit for Packetbeatedit
The systemd service unit file includes environment variables that you can override to change the default options.
Flags for configuration file path
To override these variables, create a drop-in unit file in the
For example a file with the following content placed in
BEAT_LOG_OPTS to enable debug for Elasticsearch output.
[Service] Environment="BEAT_LOG_OPTS=-e -d elasticsearch"
To change the logging output from the Packetbeat configuration file, empty the environment variable. For example:
To apply your changes, reload the systemd configuration and restart the service:
systemctl daemon-reload systemctl restart packetbeat
It is recommended that you use a configuration management tool to
include drop-in unit files. If you need to add a drop-in manually, use
systemctl edit packetbeat.service.
Intro to Kibana
ELK for Logs & Metrics