# Simple Central log monitoring with ELK **URL:** \ **Category:** Logstash\ **Created:** [August 5, 2021, 3:30am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488 "2021-08-05T03:30:56Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 5, 2021, 3:30am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/1 "2021-08-05T03:30:57Z")
Need to ship my servers logs (Linux system logs " /var/logs/\*" and windows server logs) to logstash to ELK and display in KIbana dash board. Please guide to perform this task. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 5, 2021, 3:32am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/2 "2021-08-05T03:32:12Z")
What have you tried so far? ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 5, 2021, 3:37am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/3 "2021-08-05T03:37:44Z")
Already Installed filebeat,logstash,Elasticsearch,Kibana as guide of DigitalOcean. > **[How To Install and Configure Elasticsearch on Ubuntu 20.04 | DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-elasticsearch-on-ubuntu-20-04)** > > Elasticsearch is a platform for distributed search and analysis of data in real time. This article will guide you through installing Elasticsearch, configuring it for your use case, securing your installation, and beginning to work with your... ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 5, 2021, 3:38am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/4 "2021-08-05T03:38:23Z")
But I need to ship my all servers logs to ELK ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 5, 2021, 3:43am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/5 "2021-08-05T03:43:30Z")
Ok, so what's missing that you need? ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 5, 2021, 3:47am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/6 "2021-08-05T03:47:10Z")
Please tell me how to send my server logs (Just centos6 or Centos 7 servers logs) to Stack. /var/log/_._ to ELK ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 5, 2021, 3:56am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/7 "2021-08-05T03:56:35Z")
Filebeat has modules to handle that, so definitely start by checking that. Otherwise use the standard `filestream` input. ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 5, 2021, 4:15am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/8 "2021-08-05T04:15:32Z")
So tell me what is the correct process; **server's logs** (using rsyslog client) --\> **Central rsyslog server** --\> **Filebeat+Logstash+Elasticsearch** --\> **Kibana** (Dashboard) or **servers logs** (install filebeat in each server in server farm) ---\> **Logstash+Elasticsearch** --\> **Kibana** (Dashboard) ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 5, 2021, 4:23am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/9 "2021-08-05T04:23:38Z")
There's no "correct" as either of those will work. ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 5, 2021, 4:56am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/10 "2021-08-05T04:56:13Z")
> [@Prabhath\_samarasingh](#): > > **server's logs** (using rsyslog client) --\> **Central rsyslog server** --\> **Filebeat+Logstash+Elasticsearch** --\> **Kibana** (Dashboard) Tried rsyslog method and not worked ... Can you help me to success rsyslog method, cus rsyslog already installed on default installation. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 5, 2021, 4:59am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/11 "2021-08-05T04:59:59Z")
You are going to have to be willing to share a lot more information about what you did and what is not working. ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 5, 2021, 7:40am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/12 "2021-08-05T07:40:59Z")
**Filebeat Configuration** ```auto vim /etc/filebeat/filebeat.yml output.logstash: # The Logstash hosts hosts: ["localhost:5044"] ``` **Logstash Configuration** ```auto elk@elk:/etc/logstash/conf.d$ pwd /etc/logstash/conf.d elk@elk:/etc/logstash/conf.d$ ls 02-beats-input.conf 30-elasticsearch-output.conf logstash.conf_Org_05-08-2021 elk@elk:/etc/logstash/conf.d$ ``` ```auto elk@elk:/etc/logstash/conf.d$ cat 02-beats-input.conf input { beats { port => 5044 } } elk@elk:/etc/logstash/conf.d$ elk@elk:/etc/logstash/conf.d$ cat 30-elasticsearch-output.conf output { if [@metadata][pipeline] { elasticsearch { hosts => ["localhost:9200"] manage_template => false index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}" pipeline => "%{[@metadata][pipeline]}" } } else { elasticsearch { hosts => ["localhost:9200"] manage_template => false index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}" } } } elk@elk:/etc/logstash/conf.d$ ``` **Elasticsearch Configuration** ```auto root@elk:/etc/elasticsearch# pwd /etc/elasticsearch root@elk:/etc/elasticsearch# ls elasticsearch.keystore jvm.options role_mapping.yml users_roles elasticsearch.yml jvm.options.d roles.yml elasticsearch.yml_Org log4j2.properties users root@elk:/etc/elasticsearch# ``` ```auto root@elk:/etc/elasticsearch# vim elasticsearch.yml network.host: localhost ``` ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/3/03db7e5a029c282aca605b0b71236756ce56f315.png) All working fine ... I need to **ship my linux server logs to this stack**. ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [August 5, 2021, 2:07pm UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/13 "2021-08-05T14:07:37Z")
What is the issue exactly? It looks like there are logs being shipped and visible in Kibana ... Is it that you are just not getting Linux logs but getting other logs, I don't understand the exact issue? Also you did not include the input portion of your filebeat.yml which is where your Linux logs paths would be. What exactly is the file path to linux logs? Please show where you define the filebeat input for those Linux logs ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 16, 2021, 3:24am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/14 "2021-08-16T03:24:38Z")
> [@Prabhath\_samarasingh](#): > > ```auto > elk@elk:/etc/logstash/conf.d$ cat 02-beats-input.conf > input { > beats { > port => 5044 > } > } > > ``` ```auto elk@elk:/etc/logstash/conf.d$ cat 02-beats-input.conf input { beats { port => 5044 } } elk@elk:/etc/logstash/conf.d$ elk@elk:/etc/logstash/conf.d$ cat 30-elasticsearch-output.conf output { if [@metadata][pipeline] { elasticsearch { hosts => ["localhost:9200"] manage_template => false index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}" pipeline => "%{[@metadata][pipeline]}" } } else { elasticsearch { hosts => ["localhost:9200"] manage_template => false index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}" } } } elk@elk:/etc/logstash/conf.d$ ``` ```auto Below is the input of filebeats. Is it not correct,Please correct. I received some syslogs and need to convert it to meaningful log visual format in Kibana. elk@elk:/etc/logstash/conf.d$ cat 02-beats-input.conf input { beats { port => 5044 } } ``` ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/6/96ae1e0bd7fc676335adb2ea3957da96186461a4.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/a/8a6d5a83c36eaff211ca9d034d88bb810a3b2414.png) ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 16, 2021, 3:32am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/15 "2021-08-16T03:32:01Z")
And also need to ships my mail gateway servers logs. Basically **maillogs** located at under mailservers **/var/log/** ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [August 16, 2021, 3:44am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/16 "2021-08-16T03:44:55Z")
> [@Prabhath\_samarasingh](#): > > ```auto > Below is the input of filebeats. Is it not correct,Please correct. > I received some syslogs and need to convert it to meaningful log visual format in Kibana. > > elk@elk:/etc/logstash/conf.d$ cat 02-beats-input.conf > input { > beats { > port => 5044 > } > } > > ``` No that is not the `filebeat.yml` that is the Beats Input for the logstash configurations. Please share your `filebeat.yml`. Also you have still not made it clear what the issue is in youir filebeat.yml you will need to define log inputs like the following so filebeat will pick up those logs see here > **[Log input | Filebeat Reference \[8.11\] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-log.html)** Example ```auto - type: log # Change to true to enable this input configuration. enabled: true # Paths that should be crawled and fetched. Glob based paths. paths: - /var/log/*.log ``` ---
**Author:** ![Prabhath\_samarasingh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prabhath_samarasingh/32/84203_2.png) [@Prabhath\_samarasingh](https://discuss.elastic.co/u/Prabhath_samarasingh)\ **Post date:** [August 16, 2021, 3:58am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/17 "2021-08-16T03:58:39Z")
Processing: filebeat.yml... ```auto =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.08.16 09:23:24 =~=~=~=~=~=~=~=~=~=~=~= elk@elk:~$ cat /etc/filebeat/filebeat.yml sudo ###################### 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: # https://www.elastic.co/guide/en/beats/filebeat/index.html # For more available modules and options, please see the filebeat.reference.yml sample # configuration file. # ============================== Filebeat inputs =============================== 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. - type: log # Change to true to enable this input configuration. enabled: false # Paths that should be crawled and fetched. Glob based paths. paths: - /var/log/*.log #- c:\programdata\elasticsearch\logs\* # Exclude lines. A list of regular expressions to match. It drops the lines that are # matching any regular expression from the list. #exclude_lines: ['^DBG'] # 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. #exclude_files: ['.gz$'] # Optional additional fields. These fields can be freely picked # to add additional information to the crawled log files for filtering #fields: # level: debug # review: 1 ### Multiline options # 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 [ #multiline.pattern: ^\[ # Defines if the pattern set under pattern should be negated or not. Default is false. #multiline.negate: 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 #multiline.match: after # filestream is an experimental input. It is going to replace log input in the future. - type: filestream # Change to true to enable this input configuration. enabled: false # Paths that should be crawled and fetched. Glob based paths. paths: #- /var/log/*.log - /var/log/* #- c:\programdata\elasticsearch\logs\* # Exclude lines. A list of regular expressions to match. It drops the lines that are # matching any regular expression from the list. #exclude_lines: ['^DBG'] # 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. #prospector.scanner.exclude_files: ['.gz$'] # Optional additional fields. These fields can be freely picked # to add additional information to the crawled log files for filtering #fields: # level: debug # review: 1 # ============================== Filebeat modules ============================== filebeat.config.modules: # Glob pattern for configuration loading path: ${path.config}/modules.d/*.yml # Set to true to enable config reloading reload.enabled: false # Period on which files under path should be checked for changes #reload.period: 10s # ======================= Elasticsearch template setting ======================= setup.template.settings: index.number_of_shards: 1 #index.codec: best_compression #_source.enabled: false # ================================== 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. #name: # The tags of the shipper are included in their own field with each # transaction published. #tags: ["service-X", "web-tier"] # Optional fields that you can specify to add additional information to the # output. #fields: # env: staging # ================================= 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` command. #setup.dashboards.enabled: false # 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 # website. #setup.dashboards.url: # =================================== Kibana =================================== # Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API. # This requires a Kibana endpoint configuration. setup.kibana: # Kibana Host # 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 #host: "localhost:5601" # Kibana Space ID # ID of the Kibana Space into which the dashboards should be loaded. By default, # the Default Space will be used. #space.id: # =============================== Elastic Cloud ================================ # These settings simplify using Filebeat with the Elastic Cloud (https://cloud.elastic.co/). # The cloud.id setting overwrites the `output.elasticsearch.hosts` and # `setup.kibana.host` options. # You can find the `cloud.id` in the Elastic Cloud web UI. #cloud.id: # The cloud.auth setting overwrites the `output.elasticsearch.username` and # `output.elasticsearch.password` settings. The format is `:`. #cloud.auth: # ================================== Outputs =================================== # Configure what output to use when sending the data collected by the beat. # ---------------------------- Elasticsearch Output ---------------------------- #output.elasticsearch: # Array of hosts to connect to. # hosts: ["localhost:9200"] # Protocol - either `http` (default) or `https`. #protocol: "https" # Authentication credentials - either API key or username/password. #api_key: "id:api_key" #username: "elastic" #password: "changeme" # ------------------------------ Logstash Output ------------------------------- output.logstash: # The Logstash hosts hosts: ["localhost:5044"] # Optional SSL. By default is off. # List of root certificates for HTTPS server verifications #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"] # Certificate for SSL client authentication #ssl.certificate: "/etc/pki/client/cert.pem" # Client Certificate Key #ssl.key: "/etc/pki/client/cert.key" # ================================= Processors ================================= processors: - add_host_metadata: when.not.contains.tags: forwarded - add_cloud_metadata: ~ - add_docker_metadata: ~ - add_kubernetes_metadata: ~ # ================================== Logging =================================== # Sets log level. The default log level is info. # Available log levels are: error, warning, info, debug #logging.level: debug # At debug level, you can selectively enable logging only for some components. # To enable all selectors use ["*"]. Examples of other selectors are "beat", # "publisher", "service". #logging.selectors: ["*"] # ============================= X-Pack Monitoring ============================== # Filebeat can export internal metrics to a central Elasticsearch monitoring # cluster. This requires xpack monitoring to be enabled in Elasticsearch. The # reporting is disabled by default. # Set to true to enable the monitoring reporter. #monitoring.enabled: false # Sets the UUID of the Elasticsearch cluster under which monitoring data for this # Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch # is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch. #monitoring.cluster_uuid: # Uncomment to send the metrics to Elasticsearch. Most settings from the # Elasticsearch output are accepted here as well. # Note that the settings should point to your Elasticsearch *monitoring* cluster. # Any setting that is not set is automatically inherited from the Elasticsearch # output configuration, so if you have the Elasticsearch output configured such # that it is pointing to your Elasticsearch monitoring cluster, you can simply # uncomment the following line. #monitoring.elasticsearch: # ============================== Instrumentation =============================== # Instrumentation support for the filebeat. #instrumentation: # Set to true to enable instrumentation of filebeat. #enabled: false # Environment in which filebeat is running on (eg: staging, production, etc.) #environment: "" # APM Server hosts to report instrumentation results to. #hosts: # - http://localhost:8200 # API Key for the APM Server(s). # If api_key is set then secret_token will be ignored. #api_key: # Secret token for the APM Server(s). #secret_token: # ================================= Migration ================================== # This allows to enable 6.7 migration aliases #migration.6_to_7.enabled: true logout ``` ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [August 16, 2021, 4:09am UTC](https://discuss.elastic.co/t/simple-central-log-monitoring-with-elk/280488/18 "2021-08-16T04:09:27Z")
> [@Prabhath\_samarasingh](#): > > ```auto > - type: log > > # Change to true to enable this input configuration. > enabled: false