![]() ![]() ![]() # Filebeat instance will appear in the Stack Monitoring UI. # Sets the UUID of the Elasticsearch cluster under which monitoring data for this # Set to true to enable the monitoring reporter. This requires xpack monitoring to be enabled in Elasticsearch. # Filebeat can export internal metrics to a central Elasticsearch monitoring # At debug level, you can selectively enable logging only for some components. # Available log levels are: error, warning, info, debug # Configure processors to enhance or manipulate events generated by the beat. #ssl.certificate: "/etc/pki/client/cert.pem" # Certificate for SSL client authentication # List of root certificates for HTTPS server verifications # Authentication credentials - either API key or username/password. # Protocol - either `http` (default) or `https`. # Configure what output to use when sending the data collected by the beat. # You can find the `cloud.id` in the Elastic Cloud web UI. # The cloud.id setting overwrites the `` and # These settings simplify using Filebeat with the Elastic Cloud (). # ID of the Kibana Space into which the dashboards should be loaded. # In case you specify and additional path, the scheme is required: # IPv6 addresses should always be defined as: #host: "localhost:5601" # Scheme and port can be left out and will be set to the default (http and 5601) # This requires a Kibana endpoint configuration. # Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API. # versions, this URL points to the dashboard archive on the # has a value which is computed based on the Beat name and version. # The URL from where to download the dashboards archive. # options here or by using the `setup` command. # the dashboards is disabled by default and can be enabled either by setting the # These settings control loading the sample dashboards to the Kibana index. # Optional fields that you can specify to add additional information to the # The tags of the shipper are included in their own field with each ![]() # all the transactions sent by a single shipper in the web interface. # The name of the shipper that publishes the network data. # Period on which files under path should be checked for changes # Paths that should be crawled and fetched. # Change to true to enable this input configuration. ![]() I'm trying to use fortinet module to parse and make logs presentable before it ships to logstash here is my filebeats configuration file: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |