- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- 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
- Configure index lifecycle management
- Load balance the output hosts
- Specify SSL settings
- Filter and enhance the exported data
- Define processors
- Add cloud metadata
- Add fields
- Add labels
- Add the local time zone
- Add tags
- Decode CSV fields
- Decode JSON fields
- Community ID Network Flow Hash
- Convert
- Drop events
- Drop fields from events
- Keep fields from events
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host metadata
- Add Observer metadata
- Dissect strings
- DNS Reverse Lookup
- Add process metadata
- Script Processor
- Extract array
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure project paths
- Configure 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
- Modules overview
- Apache module
- Auditd module
- Cisco module
- Coredns Module
- Elasticsearch module
- Envoyproxy Module
- haproxy module
- Icinga module
- IIS module
- Iptables module
- Kafka module
- Kibana module
- Logstash module
- MongoDB module
- MySQL module
- nats module
- NetFlow module
- Nginx module
- Osquery module
- Palo Alto Networks module
- PostgreSQL module
- RabbitMQ module
- Redis module
- Santa module
- Suricata module
- System module
- Traefik module
- Zeek (Bro) Module
- Exported fields
- Apache fields
- Auditd fields
- Beat fields
- Cisco fields
- Cloud provider metadata fields
- Coredns fields
- Docker fields
- ECS fields
- elasticsearch fields
- Envoyproxy fields
- haproxy fields
- Host fields
- Icinga fields
- IIS fields
- iptables fields
- Jolokia Discovery autodiscover provider fields
- Kafka fields
- kibana fields
- Kubernetes fields
- Log file content fields
- logstash fields
- mongodb fields
- MySQL fields
- nats fields
- NetFlow fields
- NetFlow fields
- Nginx fields
- Osquery fields
- panw fields
- PostgreSQL fields
- Process fields
- RabbitMQ fields
- Redis fields
- Google Santa fields
- Suricata fields
- System fields
- Traefik fields
- Zeek fields
- Monitoring Filebeat
- Securing Filebeat
- Troubleshooting
- Get help
- Debug
- Common problems
- Can’t read log files from network volumes
- Filebeat isn’t collecting lines from a file
- Too many open file handlers
- Registry file is too large
- Inode reuse causes Filebeat to skip lines
- Open file handlers cause issues with Windows file rotation
- Filebeat is using too much CPU
- Dashboard in Kibana is breaking up data fields incorrectly
- Fields are not indexed or usable in Kibana visualizations
- Filebeat isn’t shipping the last line of a file
- Filebeat keeps open file handlers of deleted files for a long time
- Filebeat 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
- Contributing to Beats
Regular expression support
editRegular expression support
editFilebeat regular expression support is based on RE2.
Filebeat has several configuration options that accept regular expressions.
For example, multiline.pattern
, include_lines
, exclude_lines
, and
exclude_files
all accept regular expressions. Some options, however, such as
the input paths
option, accept only glob-based paths.
Before using a regular expression in the config file, refer to the documentation to verify that the option you are setting accepts a regular expression.
We recommend that you wrap regular expressions in single quotation marks to work around YAML’s string escaping rules. For example, '^\[?[0-9][0-9]:?[0-9][0-9]|^[[:graph:]]+'
.
For more examples of supported regexp patterns, see Managing Multiline Messages. Although the examples pertain to Filebeat, the regexp patterns are applicable to other use cases.
The following patterns are supported:
Pattern | Description |
---|---|
|
single character |
|
any character |
|
character class |
|
negated character class |
|
ASCII character class |
|
negated ASCII character class |
|
Perl character class |
|
negated Perl character class |
|
Unicode character class (one-letter name) |
|
Unicode character class |
|
negated Unicode character class (one-letter name) |
|
negated Unicode character class |
|
|
|
|
|
zero or more |
|
one or more |
|
zero or one |
|
|
|
|
|
exactly |
|
zero or more |
|
one or more |
|
zero or one |
|
|
|
|
|
exactly |
|
numbered capturing group (submatch) |
|
named & numbered capturing group (submatch) |
|
non-capturing group |
|
set flags within current group, non-capturing |
|
set flags during re, non-capturing |
|
case-insensitive (default false) |
|
multi-line mode: |
|
let |
|
ungreedy: swap meaning of |
|
at beginning of text or line ( |
|
at end of text (like |
|
at beginning of text |
|
at ASCII word boundary ( |
|
not at ASCII word boundary |
|
at end of text |
|
bell (same as |
|
form feed (same as |
|
horizontal tab (same as |
|
newline (same as |
|
carriage return (same as |
|
vertical tab character (same as |
|
literal |
|
octal character code (up to three digits) |
|
two-digit hex character code |
|
hex character code |
|
literal text |
|
alphanumeric (same as |
|
alphabetic (same as |
|
ASCII (same as |
|
blank (same as |
|
control (same as |
|
digits (same as |
|
graphical (same as |
|
lower case (same as |
|
printable (same as |
|
punctuation (same as |
|
whitespace (same as |
|
upper case (same as |
|
word characters (same as |
|
hex digit (same as |
|
digits (same as |
|
not digits (same as |
|
whitespace (same as |
|
not whitespace (same as |
|
word characters (same as |
|
not word characters (same as |