- Filebeat Reference: other versions:
- Filebeat overview
- Quick start: installation and configuration
- Set up and run
- Upgrade
- How Filebeat works
- Configure
- Inputs
- Multiline messages
- AWS CloudWatch
- AWS S3
- Azure Event Hub
- Azure Blob Storage
- Benchmark
- CEL
- Cloud Foundry
- CometD
- Container
- Entity Analytics
- ETW
- filestream
- GCP Pub/Sub
- Google Cloud Storage
- HTTP Endpoint
- HTTP JSON
- journald
- Kafka
- Log
- MQTT
- NetFlow
- Office 365 Management Activity API
- Redis
- Salesforce
- Stdin
- Streaming
- Syslog
- TCP
- UDP
- Unix
- winlog
- 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
- append
- cache
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_cef
- decode_csv_fields
- decode_duration
- 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
- move_fields
- parse_aws_vpc_flow_log
- rate_limit
- registered_domain
- rename
- replace
- script
- syslog
- timestamp
- translate_ldap_attribute
- translate_sid
- truncate_fields
- urldecode
- Autodiscover
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- Instrumentation
- Feature flags
- filebeat.reference.yml
- Inputs
- 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 using an ingest pipeline
- Use environment variables in the configuration
- Avoid YAML formatting problems
- Migrate
log
input configurations tofilestream
- Migrating from a Deprecated Filebeat Module
- Modules
- Modules overview
- ActiveMQ module
- Apache module
- Auditd module
- AWS module
- AWS Fargate module
- Azure module
- CEF module
- Check Point module
- Cisco module
- CoreDNS module
- CrowdStrike module
- Cyberark PAS module
- Elasticsearch module
- Envoyproxy Module
- Fortinet module
- Google Cloud module
- Google Workspace module
- HAproxy module
- IBM MQ module
- Icinga module
- IIS 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
- Nginx module
- Office 365 module
- Okta module
- Oracle module
- Osquery module
- Palo Alto Networks module
- pensando module
- PostgreSQL module
- RabbitMQ module
- Redis module
- Salesforce module
- Santa module
- Snyk module
- Sophos module
- Suricata module
- System module
- Threat Intel module
- Traefik module
- Zeek (Bro) Module
- ZooKeeper module
- Zoom module
- Exported fields
- ActiveMQ fields
- Apache fields
- Auditd fields
- AWS fields
- AWS CloudWatch fields
- AWS Fargate fields
- Azure fields
- Beat fields
- Decode CEF processor fields fields
- CEF fields
- Checkpoint fields
- Cisco fields
- Cloud provider metadata fields
- Coredns fields
- Crowdstrike fields
- CyberArk PAS fields
- Docker fields
- ECS fields
- Elasticsearch fields
- Envoyproxy fields
- Fortinet fields
- Google Cloud Platform (GCP) fields
- google_workspace fields
- HAProxy fields
- Host fields
- ibmmq fields
- Icinga fields
- IIS fields
- iptables fields
- Jolokia Discovery autodiscover provider fields
- Juniper JUNOS fields
- Kafka fields
- kibana fields
- Kubernetes fields
- Log file content fields
- logstash fields
- Lumberjack fields
- Microsoft fields
- MISP fields
- mongodb fields
- mssql fields
- MySQL fields
- MySQL Enterprise fields
- NATS fields
- NetFlow fields
- Nginx fields
- Office 365 fields
- Okta fields
- Oracle fields
- Osquery fields
- panw fields
- Pensando fields
- PostgreSQL fields
- Process fields
- RabbitMQ fields
- Redis fields
- s3 fields
- Salesforce fields
- Google Santa fields
- Snyk fields
- sophos fields
- Suricata fields
- System fields
- threatintel fields
- Traefik fields
- Windows ETW fields
- Zeek fields
- ZooKeeper fields
- Zoom fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Understand logged metrics
- 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
- High RSS memory usage due to MADV settings
- Contribute to Beats
Juniper module
editJuniper module
editThis is a module for ingesting data from the different Juniper Products. Currently supports these filesets:
-
srx
fileset: Supports Juniper SRX logs
Read the quick start to learn how to configure and run modules.
Configure the module
editYou can further refine the behavior of the juniper
module by specifying
variable settings in the
modules.d/juniper.yml
file, or overriding settings at the command line.
You must enable at least one fileset in the module. Filesets are disabled by default.
Variable settings
editEach fileset has separate variable settings for configuring the behavior of the
module. If you don’t specify variable settings, the juniper
module uses
the defaults.
For advanced use cases, you can also override input settings. See Override input settings.
When you specify a setting at the command line, remember to prefix the
setting with the module name, for example, juniper.{fileset_ex}.var.paths
instead of {fileset_ex}.var.paths
.
This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
srx
fileset settings
editThe Juniper-SRX module only supports syslog messages in the format "structured-data + brief" JunOS Documentation structured-data
To configure a remote syslog destination, please reference the SRX Getting Started - Configure System Logging.
The following processes and tags are supported:
JunOS processes | JunOS tags | |
---|---|---|
RT_FLOW |
RT_FLOW_SESSION_CREATE |
|
RT_FLOW_SESSION_CLOSE |
||
RT_FLOW_SESSION_DENY |
||
APPTRACK_SESSION_CREATE |
||
APPTRACK_SESSION_CLOSE |
||
APPTRACK_SESSION_VOL_UPDATE |
||
RT_IDS |
RT_SCREEN_TCP |
|
RT_SCREEN_UDP |
||
RT_SCREEN_ICMP |
||
RT_SCREEN_IP |
||
RT_SCREEN_TCP_DST_IP |
||
RT_SCREEN_TCP_SRC_IP |
||
RT_UTM |
WEBFILTER_URL_PERMITTED |
|
WEBFILTER_URL_BLOCKED |
||
AV_VIRUS_DETECTED_MT |
||
CONTENT_FILTERING_BLOCKED_MT |
||
ANTISPAM_SPAM_DETECTED_MT |
||
RT_IDP |
IDP_ATTACK_LOG_EVENT |
|
IDP_APPDDOS_APP_STATE_EVENT |
||
RT_AAMW |
SRX_AAMW_ACTION_LOG |
|
AAMW_MALWARE_EVENT_LOG |
||
AAMW_HOST_INFECTED_EVENT_LOG |
||
AAMW_ACTION_LOG |
||
RT_SECINTEL |
SECINTEL_ACTION_LOG |
The syslog format choosen should be Default
.
Compatibility
editThis module has been tested against JunOS version 19.x and 20.x. Versions above this are expected to work but have not been tested.
- module: juniper junos: enabled: true var.input: udp var.syslog_host: 0.0.0.0 var.syslog_port: 9006
-
var.paths
-
An array of glob-based paths that specify where to look for the log files. All
patterns supported by Go Glob
are also supported here. For example, you can use wildcards to fetch all files
from a predefined level of subdirectories:
/path/to/log/*/*.log
. This fetches all.log
files from the subfolders of/path/to/log
. It does not fetch log files from the/path/to/log
folder itself. If this setting is left empty, Filebeat will choose log paths based on your operating system. -
var.input
-
The input to use, can be either the value
tcp
,udp
orfile
. -
var.syslog_host
- The interface to listen to all syslog traffic. Defaults to localhost. Set to 0.0.0.0 to bind to all available interfaces.
-
var.syslog_port
- The port to listen for syslog traffic. Defaults to 9006.
Juniper SRX ECS fields
editThis is a list of JunOS fields that are mapped to ECS.
Juniper SRX Fields | ECS Fields | |
---|---|---|
application-risk |
event.risk_score |
|
bytes-from-client |
source.bytes |
|
bytes-from-server |
destination.bytes |
|
destination-interface-name |
observer.egress.interface.name |
|
destination-zone-name |
observer.egress.zone |
|
destination-address |
destination.ip |
|
destination-port |
destination.port |
|
dst_domainname |
url.domain |
|
elapsed-time |
event.duration |
|
filename |
file.name |
|
nat-destination-address |
destination.nat.ip |
|
nat-destination-port |
destination.nat.port |
|
nat-source-address |
source.nat.ip |
|
nat-source-port |
source.nat.port |
|
message |
message |
|
obj |
url.path |
|
packets-from-client |
source.packets |
|
packets-from-server |
destination.packets |
|
policy-name |
rule.name |
|
protocol |
network.transport |
|
source-address |
source.ip |
|
source-interface-name |
observer.ingress.interface.name |
|
source-port |
source.port |
|
source-zone-name |
observer.ingress.zone |
|
url |
url.domain |
Fields
editFor a description of each field in the module, see the exported fields section.
On this page
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now