Skip to main content

Push logs and data into elasticsearch - Part 1 NGINX

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs.

Prerequesites:
You'll need a working Elasticsearch Cluster with Logstash and Kibana and an installation of Filebeat on the Host(s) where you get your nginx logs from.

Start by getting the Log Data you want to structure parsed correctly.
The nginx logs are pretty straight forward, so after checking them out in the grok debugger, I'll have the following structure mapped:
 %{IP:ClientIP} - %{DATA:username} \[%{NGINXTIMESTAMP:timestamp}%{GREEDYDATA}\] \"%{WORD:method} %{DATA:request_uri} %{DATA:http-version}\" %{RETURNCODE:http_return_code} %{GREEDYDATA} \"%{DATA:server_name}\" \"%{GREEDYDATA}\"
Also, I've written some custom patterns:
 NGINXTIMESTAMP (?:(?:0[1-9])|(?:[12][0-9])|(?:3[01])|[1-9])\/\b(?:[Jj]an(?:uary|uar)?|[Ff]eb(?:ruary|ruar)?|[Mm](?:a|ä)?r(?:ch|z)?|[Aa]pr(?:il)?|[Mm]a(?:y|i)?|[Jj]un(?:e|i)?|[Jj]ul(?:y)?|[Aa]ug(?:ust)?|[Ss]ep(?:tember)?|[Oo](?:c|k)?t(?:ober)?|[Nn]ov(?:ember)?|[Dd]e(?:c|z)(?:ember)?)\b\/(?>\d\d){1,2}\:(?:2[0123]|[01]?[0-9]):(?:[0-5][0-9]):(?:(?:[0-5]?[0-9]|60)(?:[:.,][0-9]+)?)  
 RETURNCODE [1-5][0-9][0-9]
With that we can build a pipeline that looks like so:
 [archy@elk01 ~]$ cat /etc/logstash/conf.d/nginx.conf  
 # Input will be the filebeat installed on the host  
 input {  
  beats {  
   port => 5044  
  }  
 }  
 # the tag nginx-log will be sent by filebeat  
 filter {  
  if "nginx-log" in [tags] {  
   grok {  
    id => "nginx-pipeline"  
    patterns_dir => "/etc/logstash/custom-patterns/"  
    tag_on_failure => "_grokparsefailure_nginx"  
    match => [  
      "message", "%{IP:ClientIP} - %{DATA:username} \[%{NGINXTIMESTAMP:timestamp}%{GREEDYDATA}\] \"%{WORD:method} %{DATA:request_uri} %{DATA:http-version}\" %{RETURNCODE:http_return_code} %{GREEDYDATA} \"%{DATA:server_name}\" \"%{GREEDYDATA}\""  
    ]  
   }  
   if "_grokparsefailure_nginx" not in [tags] {  
    mutate {  
     remove_field => ["message"]  
    }  
   }  
  }  
 }  
 # output to all elasticsearch hosts  
 output {  
  if "nginx-log" in [tags] {  
   elasticsearch {  
    id => "nginx-output"  
    hosts => ["http://elk01.archyslife.lan:11920", "http://elk02.archyslife.lan:11920", "http://elk03.archyslife.lan:11920", "http://elk04.archyslife.lan:11920", "http://elk05.archyslife.lan:11920"]  
    index => "nginx-log-%{+YYYY.MM.ww}"  
   }  
  }  
 }
Next up, add the following lines to your pipelines.yml
 - pipeline.id: nginx  
   path.config: "/etc/logstash/conf.d/nginx.conf"
Logstash is configured, next up create the Index Template for the data. The Index Template will essentially tell elasticsearch what data will be stored in what way.
Note: You'll need to run this in the DevTools Console in your Kibana instance or by using Curl with 'XPUT' against the elasticsearch api.
 PUT _template/nginx-log  
 {  
   "index_patterns" : [  
    "nginx-log-*"  
   ],  
   "settings" : {  
    "index" : {  
     "codec" : "best_compression",  
     "refresh_interval" : "5s",  
     "number_of_shards" : "1",  
     "number_of_replicas" : "1"  
    }  
   },  
   "mappings" : {  
    "doc" : {  
     "numeric_detection" : true,  
     "dynamic_templates" : [  
      {  
       "string_fields" : {  
        "mapping" : {  
         "type" : "keyword"  
        },  
        "match_mapping_type" : "string",  
        "match" : "*"  
       }  
      }  
     ],  
     "properties" : {  
      "@version" : {  
       "type" : "keyword"  
      },  
      "@timestamp" : {  
       "type" : "date"  
      },  
      "date" : {  
       "type" : "keyword"  
      },  
      "time" : {  
       "type" : "keyword"  
      },  
      "ClientIP" : {  
       "type" : "keyword"  
      },  
      "username" : {  
       "type" : "keyword"  
      },  
      "method" : {  
       "type" : "keyword"  
      },  
      "request_uri" : {  
       "type" : "text"  
      },  
      "http-version" : {  
       "type" : "text"  
      },  
      "http_return_code" : {  
       "type" : "keyword"  
      },  
      "server_name" : {  
       "type" : "keyword"  
      }  
     }  
    }  
   },  
   "aliases" : { }  
  }
Elasticsearch is setup and we can continue to install and configure filebeat on the server running nginx:
 [archy@nginx01 ~]$ sudo yum -y localinstall filebeat-6.7.2.rpm
Here's a short example of my filebeat config:
 [archy@nginx01 ~]$ sudo vim /etc/filebeat/filebeat.yml  

 filebeat.inputs:  
 - type: log  
  enabled: true  
  paths:  
   - /var/log/nginx/http_intranet.archyslife.lan-access.log  
   - /var/log/nginx/http_intranet.archyslife.lan-error.log  
   - /var/log/nginx/https_intranet.archyslife.lan-accress.log  
   - /var/log/nginx/https_intranet.archyslife.lan-error.log  
   - /var/log/nginx/http_elastic-api.archyslife.lan-access.log  
   - /var/log/nginx/http_elastic-api.archyslife.lan-error.log  
   - /var/log/nginx/http_kibana.archyslife.lan-access.log  
   - /var/log/nginx/http_kibana.archyslife.lan-error.log  
 filebeat.config.modules:  
  path: ${path.config}/modules.d/*.yml  
  reload.enabled: false  
 setup.template.settings:  
  index.number_of_shards: 3  
 tags: ["nginx-log"]  
 output.logstash:  
  hosts: ["elk01.archyslife.lan:5044", "elk02.archyslife.lan:5044"]  
 processors:
The last step is to enable and start filebeat:
 [archy@nginx01 ~]$ systemctl enable filebeat.service  
 [archy@nginx01 ~]$ systemctl start filebeat.service
Filebeat will now push data into your Cluster. To make the Data visible, however, kibana needs to have an Index pattern created. You can do this from the web interface itself by doing the following
--> Click on 'Management'
--> Click on 'Index Patterns' in the Kibana section
--> Click on the 'Create Index Pattern' button in the top left corner and type in the index name. In my case, it's 'nginx-log*'
--> Click on 'Next Step', select the Time Filter field name and click on 'Create Index pattern'

Your data is now indexed in elasticsearch and visible in kibana.

If there are any _grokparsefailure, you'll need to check your message pattern with the grok debugger which can be found in the Dev Tools.

Feel free to comment and / or suggest a topic.
Labels:

Comments

Post a Comment

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0
Post a Comment
Read more

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla
8 comments
Read more

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?
9 comments
Read more

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). recently went over my network configuration and I noticed that I've never put my My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key&quo
2 comments
Read more

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the
Post a Comment
Read more