- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- Step 1: Install Filebeat
- Step 2: Configure Filebeat
- Step 3: Configure Filebeat to use Logstash
- Step 4: Load the index template in Elasticsearch
- Step 5: Set up the Kibana dashboards
- Step 6: Start Filebeat
- Step 7: View the sample Kibana dashboards
- Quick start: modules for common log formats
- Repositories for APT and YUM
- Setting up and running Filebeat
- Upgrading Filebeat
- How Filebeat works
- Configuring Filebeat
- Specify which modules to run
- Configure inputs
- Manage multiline messages
- Specify general settings
- Load external configuration files
- Configure the internal queue
- Configure the output
- Set up index lifecycle management
- Load balance the output hosts
- Specify SSL settings
- Filter and enhance the exported data
- Parse data by using ingest node
- Enrich events with geoIP information
- 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
- Autodiscover
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- filebeat.reference.yml
- Beats central management
- Modules
- Exported fields
- Alias fields
- Apache2 fields
- Auditd fields
- Beat fields
- Cloud provider metadata fields
- Docker fields
- elasticsearch fields
- haproxy fields
- Host fields
- Icinga fields
- IIS fields
- Kafka fields
- kibana fields
- Kubernetes fields
- Log file content fields
- logstash fields
- mongodb fields
- MySQL fields
- Nginx fields
- Osquery fields
- PostgreSQL fields
- Redis fields
- System fields
- Traefik fields
- Monitoring Filebeat
- Securing Filebeat
- Troubleshooting
- Migrating from Logstash Forwarder to Filebeat
- Contributing to Beats
Auditd fields
editAuditd fields
editModule for parsing auditd logs.
auditd fields
editFields from the auditd logs.
log fields
editFields from the Linux audit log. Not all fields are documented here because they are dynamic and vary by audit event type.
-
auditd.log.record_type -
The audit event type.
-
auditd.log.old_auid -
For login events this is the old audit ID used for the user prior to this login.
-
auditd.log.new_auid -
For login events this is the new audit ID. The audit ID can be used to trace future events to the user even if their identity changes (like becoming root).
-
auditd.log.old_ses -
For login events this is the old session ID used for the user prior to this login.
-
auditd.log.new_ses -
For login events this is the new session ID. It can be used to tie a user to future events by session ID.
-
auditd.log.sequence -
type: long
The audit event sequence number.
-
auditd.log.acct -
The user account name associated with the event.
-
auditd.log.pid -
The ID of the process.
-
auditd.log.ppid -
The ID of the process.
-
auditd.log.items -
The number of items in an event.
-
auditd.log.item -
The item field indicates which item out of the total number of items. This number is zero-based; a value of 0 means it is the first item.
-
auditd.log.a0 -
The first argument to the system call.
-
auditd.log.res -
The result of the system call (success or failure).
geoip fields
editContains GeoIP information gathered based on the auditd.log.addr field. Only present if the GeoIP Elasticsearch plugin is available and used.
-
auditd.log.geoip.continent_name -
type: keyword
The name of the continent.
-
auditd.log.geoip.city_name -
type: keyword
The name of the city.
-
auditd.log.geoip.region_name -
type: keyword
The name of the region.
-
auditd.log.geoip.country_iso_code -
type: keyword
Country ISO code.
-
auditd.log.geoip.location -
type: geo_point
The longitude and latitude.
-
auditd.log.geoip.region_iso_code -
type: keyword
Region ISO code.
On this page