Type to search.

Start Auditbeat

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    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.

Before starting Auditbeat:

To start Auditbeat, run:

Shell 
sudo service auditbeat start

Also see Auditbeat and systemd.

Shell 
sudo service auditbeat start

Also see Auditbeat and systemd.

Shell 
sudo chown root auditbeat.yml
sudo ./auditbeat -e
  1. You’ll be running Auditbeat as root, so you need to change ownership of the configuration file, or run Auditbeat with --strict.perms=false specified. See Config File Ownership and Permissions.
Shell 
sudo chown root auditbeat.yml
sudo ./auditbeat -e
  1. You’ll be running Auditbeat as root, so you need to change ownership of the configuration file, or run Auditbeat with --strict.perms=false specified. See Config File Ownership and Permissions.
Shell 
PS C:\Program Files\auditbeat> Start-Service auditbeat

By default Windows log files are stored in C:\Program Files\Auditbeat-Data\logs.

Note

In versions before 9.0.6, the default location for Windows log files was C:\ProgramData\auditbeat\logs.