- Filebeat Reference: other versions:
- Filebeat overview
- Quick start: installation and configuration
- Set up and run
- Upgrade
- How Filebeat works
- Configure
- Inputs
- Modules
- General settings
- Project paths
- Config file loading
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Kibana endpoint
- Kibana dashboards
- Processors
- Define processors
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_cef
- decode_csv_fields
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- rate_limit
- registered_domain
- rename
- script
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Autodiscover
- Internal queue
- Load balancing
- Logging
- HTTP endpoint
- Regular expression support
- Instrumentation
- filebeat.reference.yml
- How to guides
- Override configuration settings
- Load the Elasticsearch index template
- Change the index name
- Load Kibana dashboards
- Load ingest pipelines
- Enrich events with geoIP information
- Deduplicate data
- Parse data by using ingest node
- Use environment variables in the configuration
- Avoid YAML formatting problems
- Modules
- Modules overview
- ActiveMQ module
- Apache module
- Auditd module
- AWS module
- AWS Fargate module
- Azure module
- Barracuda module
- Bluecoat module
- CEF module
- Check Point module
- Cisco module
- CoreDNS module
- Crowdstrike module
- Cyberark module
- Cyberark PAS module
- Cylance module
- Elasticsearch module
- Envoyproxy Module
- F5 module
- Fortinet module
- Google Cloud module
- Google Workspace module
- GSuite module
- HAproxy module
- IBM MQ module
- Icinga module
- IIS module
- Imperva module
- Infoblox module
- Iptables module
- Juniper module
- Kafka module
- Kibana module
- Logstash module
- Microsoft module
- MISP module
- MongoDB module
- MSSQL module
- MySQL module
- MySQL Enterprise module
- NATS module
- NetFlow module
- Netscout module
- Nginx module
- Office 365 module
- Okta module
- Oracle module
- Osquery module
- Palo Alto Networks module
- pensando module
- PostgreSQL module
- Proofpoint module
- RabbitMQ module
- Radware module
- Redis module
- Santa module
- Snort module
- Snyk module
- Sonicwall module
- Sophos module
- Squid module
- Suricata module
- System module
- Threat Intel module
- Tomcat module
- Traefik module
- Zeek (Bro) Module
- ZooKeeper module
- Zoom module
- Zscaler module
- Exported fields
- ActiveMQ fields
- Apache fields
- Auditd fields
- AWS fields
- aws-cloudwatch fields
- AWS Fargate fields
- Azure fields
- Barracuda Web Application Firewall fields
- Beat fields
- Blue Coat Director fields
- Decode CEF processor fields fields
- CEF fields
- Checkpoint fields
- Cisco fields
- Cloud provider metadata fields
- Coredns fields
- Crowdstrike fields
- Cyber-Ark fields
- CyberArk PAS fields
- CylanceProtect fields
- Docker fields
- ECS fields
- Elasticsearch fields
- Envoyproxy fields
- Big-IP Access Policy Manager fields
- Fortinet fields
- Google Cloud Platform (GCP) fields
- google_workspace fields
- gsuite fields
- HAProxy fields
- Host fields
- ibmmq fields
- Icinga fields
- IIS fields
- Imperva SecureSphere fields
- Infoblox NIOS fields
- iptables fields
- Jolokia Discovery autodiscover provider fields
- Juniper JUNOS fields
- Kafka fields
- kibana fields
- Kubernetes fields
- Log file content fields
- logstash fields
- Microsoft fields
- MISP fields
- mongodb fields
- mssql fields
- MySQL fields
- MySQL Enterprise fields
- NATS fields
- NetFlow fields
- Arbor Peakflow SP fields
- Nginx fields
- Office 365 fields
- Okta fields
- Oracle fields
- Osquery fields
- panw fields
- Pensando fields
- PostgreSQL fields
- Process fields
- Proofpoint Email Security fields
- RabbitMQ fields
- Radware DefensePro fields
- Redis fields
- s3 fields
- Google Santa fields
- Snort/Sourcefire fields
- Snyk fields
- Sonicwall-FW fields
- sophos fields
- Squid fields
- Suricata fields
- System fields
- threatintel fields
- Apache Tomcat fields
- Traefik fields
- Zeek fields
- ZooKeeper fields
- Zoom fields
- Zscaler NSS fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Common problems
- Error extracting container id while using Kubernetes metadata
- 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
- Log rotation results in lost or duplicate events
- 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
- Publishing to Logstash fails with "connection reset by peer" message
- @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
- Dashboard could not locate the index-pattern
- Contribute to Beats
PostgreSQL fields
editPostgreSQL fields
editModule for parsing the PostgreSQL log files.
postgresql
editFields from PostgreSQL logs.
log
editFields from the PostgreSQL log files.
-
postgresql.log.timestamp
-
[7.3.0] Deprecated in 7.3.0.
The timestamp from the log line.
-
postgresql.log.core_id
-
[8.0.0] Deprecated in 8.0.0.
Core id. (deprecated, there is no core_id in PostgreSQL logs, this is actually session_line_number).
type: alias
alias to: postgresql.log.session_line_number
-
postgresql.log.client_addr
-
Host where the connection originated from.
example: 127.0.0.1
-
postgresql.log.client_port
-
Port where the connection originated from.
example: 59700
-
postgresql.log.session_id
-
PostgreSQL session.
example: 5ff1dd98.22
-
postgresql.log.session_line_number
-
Line number inside a session. (%l in
log_line_prefix
).type: long
-
postgresql.log.database
-
Name of database.
example: postgres
-
postgresql.log.query
-
Query statement. In the case of CSV parse, look at command_tag to get more context.
example: SELECT * FROM users;
-
postgresql.log.query_step
-
Statement step when using extended query protocol (one of statement, parse, bind or execute).
example: parse
-
postgresql.log.query_name
-
Name given to a query when using extended query protocol. If it is "<unnamed>", or not present, this field is ignored.
example: pdo_stmt_00000001
-
postgresql.log.command_tag
-
Type of session’s current command. The complete list can be found at: src/include/tcop/cmdtaglist.h
example: SELECT
-
postgresql.log.session_start_time
-
Time when this session started.
type: date
-
postgresql.log.virtual_transaction_id
-
Backend local transaction id.
-
postgresql.log.transaction_id
-
The id of current transaction.
type: long
-
postgresql.log.sql_state_code
-
State code returned by Postgres (if any). See also https://www.postgresql.org/docs/current/errcodes-appendix.html
type: keyword
-
postgresql.log.detail
-
More information about the message, parameters in case of a parametrized query. e.g. Role \"user\" does not exist., parameters: $1 = 42, etc.
-
postgresql.log.hint
-
A possible solution to solve an error.
-
postgresql.log.internal_query
-
Internal query that led to the error (if any).
-
postgresql.log.internal_query_pos
-
Character count of the internal query (if any).
type: long
-
postgresql.log.context
-
Error context.
-
postgresql.log.query_pos
-
Character count of the error position (if any).
type: long
-
postgresql.log.location
-
Location of the error in the PostgreSQL source code (if log_error_verbosity is set to verbose).
-
postgresql.log.application_name
-
Name of the application of this event. It is defined by the client.
-
postgresql.log.backend_type
-
Type of backend of this event. Possible types are autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, startup, walreceiver, walsender and walwriter. In addition, background workers registered by extensions may have additional types.
example: client backend
-
postgresql.log.error.code
-
[8.0.0] Deprecated in 8.0.0.
Error code returned by Postgres (if any). Deprecated: errors can have letters. Use sql_state_code instead.
type: alias
alias to: postgresql.log.sql_state_code
-
postgresql.log.timezone
-
type: alias
alias to: event.timezone
-
postgresql.log.user
-
type: alias
alias to: user.name
-
postgresql.log.level
-
Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, INFO, NOTICE, WARNING, ERROR, LOG, FATAL, and PANIC.
type: alias
example: LOG
alias to: log.level
-
postgresql.log.message
-
type: alias
alias to: message
On this page