First, I have injected my filebeat log to elsticsearch by logstash. It shows me the logs in kibana as well, manually I can even created a metric count for login attempts successfully.
However, after then I enable the default dashboard of filebeat, It don't show me dashboard output.
My configuration of filebeat.yml is following, [Here
############### Filebeat Configuration Example ###############
This file is an example configuration file highlighting only the most common
options. The filebeat.reference.yml file from the same directory contains all the
supported options with more comments. You can use it as a reference.
You can find the full configuration reference here:
For more available modules and options, please see the filebeat.reference.yml sample
#================== Filebeat inputs ==============
Each - is an input. Most options can be set at the input level, so
you can use different inputs for various configurations.
Below are the input specific configurations.
Change to true to enable this input configuration.
Paths that should be crawled and fetched. Glob based paths.
** - /var/log/messages**
** - /var/log/firewalld**
** - /var/log/yum.log**
Exclude lines. A list of regular expressions to match. It drops the lines that are
matching any regular expression from the list.
Include lines. A list of regular expressions to match. It exports the lines that are
matching any regular expression from the list.
#include_lines: ['^ERR', '^WARN']
Exclude files. A list of regular expressions to match. Filebeat drops the files that
are matching any regular expression from the list. By default, no files are dropped.
Optional additional fields. These fields can be freely picked
to add additional information to the crawled log files for filtering
Multiline can be used for log messages spanning multiple lines. This is common
for Java Stack Traces or C-Line Continuation
The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
Defines if the pattern set under pattern should be negated or not. Default is false.
Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
that was (not) matched before or after or as long as a pattern is not matched based on negate.
Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
#============== Filebeat modules ==========
Glob pattern for configuration loading
Set to true to enable config reloading
Period on which files under path should be checked for changes
#============== Elasticsearch template setting ==============
#=================== General =============
The name of the shipper that publishes the network data. It can be used to group
all the transactions sent by a single shipper in the web interface.
The tags of the shipper are included in their own field with each
#tags: ["service-X", "web-tier"]
Optional fields that you can specify to add additional information to the
#=============== Dashboards =============
These settings control loading the sample dashboards to the Kibana index. Loading
the dashboards is disabled by default and can be enabled either by setting the
options here, or by using the
-setup CLI flag or the
The URL from where to download the dashboards archive. By default this URL
has a value which is computed based on the Beat name and version. For released
versions, this URL points to the dashboard archive on the artifacts.elastic.co
#==================== Kibana ================
Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
This requires a Kibana endpoint configuration.
Scheme and port can be left out and will be set to the default (http and 5601)
In case you specify and additional path, the scheme is required: http://localhost:5601/path
IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
Kibana Space ID
ID of the Kibana Space into which the dashboards should be loaded. By default,
the Default Space will be used.
#=============== Elastic Cloud ============
These settings simplify using filebeat with the Elastic Cloud (https://cloud.elastic.co/).
The cloud.id setting overwrites the
You can find the
cloud.id in the Elastic Cloud web UI.
The cloud.auth setting overwrites the
output.elasticsearch.password settings. The format is
#====================== Outputs =================
Configure what output to use when sending the data collected by the beat.
#-------------------------- Elasticsearch output ------------------------------
Array of hosts to connect to.
Enabled ilm (beta) to use index lifecycle management instead daily indices.
Optional protocol and basic auth credentials.
#----------------------- Logstash output -------------------
The Logstash hosts
Optional SSL. By default is off.
List of root certificates for HTTPS server verifications
Certificate for SSL client authentication
Client Certificate Key
#===================== Processors ==========
Configure processors to enhance or manipulate events generated by the beat.
- add_host_metadata: ~
- add_cloud_metadata: ~
Please let me know where I am wrong?