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
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
You can use
BEAT_LOG_OPTS to set debug selectors for logging. However,
to configure logging behavior, set the logging options described in
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=-d elasticsearch"
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