- Auditbeat Reference: other versions:
- Overview
- Get started
- Set up and run
- Upgrade Auditbeat
- Configure
- Modules
- General settings
- Project paths
- Config file reloading
- Output
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Kibana endpoint
- Kibana dashboards
- Processors
- Define processors
- add_cloud_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_json_fields
- decompress_gzip_field
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- registered_domain
- rename
- truncate_fields
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- auditbeat.reference.yml
- How to guides
- Modules
- Exported fields
- Monitor
- Secure
- Troubleshoot
- Get Help
- Debug
- Common problems
- Auditbeat fails to watch folders because too many files are open
- Auditbeat uses too much bandwidth
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
- Contribute to Beats
Auditbeat and systemd
editAuditbeat and systemd
editThe DEB and RPM packages include a service unit for Linux systems with systemd. On these systems, you can manage Auditbeat by using the usual systemd commands.
Start and stop Auditbeat
editUse systemctl to start or stop Auditbeat:
systemctl start auditbeat
systemctl stop auditbeat
By default, the Auditbeat service starts automatically when the system boots. To enable or disable auto start use:
systemctl enable auditbeat
systemctl disable auditbeat
Auditbeat status and logs
editTo get the service status, use systemctl:
systemctl status auditbeat
Logs are stored by default in journald. To view the Logs, use journalctl:
journalctl -u auditbeat.service
The unit file included in the packages sets the -e flag by default.
This flag makes Auditbeat log to stderr and disables other log outputs.
Systemd stores all output sent to stderr in journald.
Customize systemd unit for Auditbeat
editThe systemd service unit file includes environment variables that you can override to change the default options.
| Variable | Description | Default value |
|---|---|---|
BEAT_LOG_OPTS |
Log options |
|
BEAT_CONFIG_OPTS |
Flags for configuration file path |
|
BEAT_PATH_OPTS |
Other paths |
|
To override these variables, create a drop-in unit file in the
/etc/systemd/system/auditbeat.service.d directory.
For example a file with the following content placed in
/etc/systemd/system/auditbeat.service.d/debug.conf
would override BEAT_LOG_OPTS to enable debug for Elasticsearch output.
[Service] Environment="BEAT_LOG_OPTS=-e -d elasticsearch"
To change the logging output from the Auditbeat configuration file, empty the environment variable. For example:
[Service] Environment="BEAT_LOG_OPTS="
To apply your changes, reload the systemd configuration and restart the service:
systemctl daemon-reload systemctl restart auditbeat
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 auditbeat.service.