- Auditbeat Reference: other versions:
- Overview
- Getting started with Auditbeat
- Breaking changes in 6.2
- Setting up and running Auditbeat
- Configuring Auditbeat
- Specify which modules to run
- Specify general settings
- Reload the configuration dynamically
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and enhance the exported data
- Parse data by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- auditbeat.reference.yml
- Modules
- Exported fields
- Monitoring Auditbeat
- Securing Auditbeat
- Troubleshooting
- Contributing to Beats
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Cloud provider metadata fields
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Cloud provider metadata fields
editMetadata from cloud providers added by the add_cloud_metadata processor.
-
meta.cloud.provider -
example: ec2
Name of the cloud provider. Possible values are ec2, gce, or digitalocean.
-
meta.cloud.instance_id -
Instance ID of the host machine.
-
meta.cloud.instance_name -
Instance name of the host machine.
-
meta.cloud.machine_type -
example: t2.medium
Machine type of the host machine.
-
meta.cloud.availability_zone -
example: us-east-1c
Availability zone in which this host is running.
-
meta.cloud.project_id -
example: project-x
Name of the project in Google Cloud.
-
meta.cloud.region -
Region in which this host is running.
Was this helpful?
Thank you for your feedback.