Filebeat setup for cakephp logs

Elastic Stack Elasticsearch
22

@stephenb

There was an typo mistake I entered 173 instead of 172.

Below is my output of you asked above. You are correct it's probably SSL issue.. can you check this..

Output of filebeat test output command:
elasticsearch: https://172.31.59.112:9200...
  parse url... OK
  connection...
    parse host... OK
    dns lookup... OK
    addresses: 172.31.59.112
    dial up... OK
  TLS...
    security: server's certificate chain verification is enabled
    handshake... ERROR x509: certificate signed by unknown authority
===============================================================================================
filebeat.yml file output section:
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["https://172.31.59.112:9200"]
===============================================================================================
Output of curl -k -v -u elastic https://172.31.59.112:9200
*   Trying 172.31.59.112:9200...
* TCP_NODELAY set
* Connected to 172.31.59.112 (172.31.59.112) port 9200 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=ip-172-31-59-112
*  start date: Aug  3 13:42:39 2023 GMT
*  expire date: Aug  2 13:42:39 2025 GMT
*  issuer: CN=Elasticsearch security auto-configuration HTTP CA
*  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
* Server auth using Basic with user 'elastic'
> GET / HTTP/1.1
> Host: 172.31.59.112:9200
> Authorization: Basic ZWxhc3RpYzpzdGFnaW5n
> User-Agent: curl/7.68.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< X-elastic-product: Elasticsearch
< content-type: application/json
< content-length: 526
<
{
  "name" : "elk",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "Mg1RZm6cR9ymnKDIXDbgXg",
  "version" : {
    "number" : "8.9.0",
    "build_flavor" : "default",
    "build_type" : "deb",
    "build_hash" : "8aa461beb06aa0417a231c345a1b8c38fb498a0d",
    "build_date" : "2023-07-19T14:43:58.555259655Z",
    "build_snapshot" : false,
    "lucene_version" : "9.7.0",
    "minimum_wire_compatibility_version" : "7.17.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "You Know, for Search"
}
* Connection #0 to host 172.31.59.112 left intact
23

As I thought you need to provide the CA or not verify which is fine for testing see here

in the

output.elasticsearch:
...
  ssl.verification_mode: none
24

@stephenb

Thank you, Now it's working.

1 Like
25

Cool now you can work back to working with Logstash if you want.

26

@stephenb

I didn't get what you're are saying.

Is it possible to send these logs to logstash output now. Actually it's working with elasticsearch out after I ran this command filebeat set -e.

But the issue is I configured the apache logs also in this server. I send apache logs via apache module to logstash output. so I can't setup both output in same filebeat.yml file.

27

You can send all your logs Custom, Modules etc. through logstash or not...

Filebeat > Logstash > Elasticsearch

Or direct probably easier and parse custom logs with ingest pipelines

Filebeat > Elasticsearch

There are some pros and cons of each ...

You need to decide what you want to do

You can not send directly to Elasticsearch and Logstash at the same time.

28

@stephenb

Currently I sending apache webserver access logs and error logs via apache module. For that I configured the output.logstash: in filebeat.yml.

And for now I also want to send cakephp logs also to logstash, then I will parse this logs using the file i mentioned in logstash/ conf.d/cakephp.conf file.

For this can you provide any steps for this. I tried multiple ways but I can't make to work this as I expected. This's more helpful for complete this setup.

29

If you configured this ALL logs collected by filebeat will go to logstash so your cake logs are going to logstash modules (apache) inputs cake ALL go to logstash.

I suspect you are having issues on the logstash side.

What you really should do is put this as the bottom of the output section in your logstash conf to see what you are getting, this is a great way to debug

stdout {}

Get each of your sources working in an iterative

Regarding apache if you properly use the module you would not need to parse in logstash...

Did you read

If you really want help you need to provide your complete configs for both parts...

30

@stephenb

below is my all the configuration file's.

This is logstash file (logstash/conf.d/apache..conf)

input {
  beats {
     port => 5044
 }
}

filter {
    if [log][file][path] in ["/var/log/apache2/sfsite-access_log","/var/log/apache2/sfapi-access_log"] {
      grok {
        match => { "message" => "\[%{HTTPDATE:time_stamp}\] %{HOSTNAME:domain_name} \"%{WORD:method} /%{NOTSPACE:request_page} HTTP/%{NUMBER:http_version}\" %{NUMBER:response_code} (?:%{NUMBER:response_bytes}|-)  %{QS:agent} %{NOTSPACE:page_url} %{QS:agent_type}" }

 }
      grok {
        match => { "message" => "%{IP:client_ip}" }
 }
      geoip {
        source => "[client_ip]"
        ecs_compatibility => disabled
      }
      mutate { remove_field => [ "[cloud][availability_zone]","[cloud][region]", "[cloud][provider]", "[host][id]", "[host][ip]", "[host][name]", "[host][mac]" ] }
      mutate { remove_field => [ "[cloud][instance][id]", "[cloud][image][id]", "[cloud][machine][type]", "[cloud][service][name]", "[cloud][account][id]", "[host][os][codename]", "[host][os][family]", "[host][os][kernel]", "[host][os][name]", "[host][os][platform]", "[host][os][type]", "[host][os][version]", "[cloud][instance][name]" ] }
}

else if [log][file][path] in ["/var/log/apache2/sfsite-error_log","/var/log/apache2/sfapi-error_log"] {
      grok {
        match => { "message" => "\[%{HTTPDERROR_DATE:timestamp-error}\] \[%{DATA:loglevel}%{SPACE}\] \[%{DATA:process-id}%{SPACE}\]%{SPACE}\[%{DATA:client-ip}\] %{GREEDYDATA:message} (\[%{NOTSPACE:Index}\]\[%{NUMBER:shards}\])?%{GREEDYDATA} %{GREEDYDATA:referred_url}" }
   }
     mutate { remove_field => [ "[cloud][availability_zone]","[cloud][region]", "[cloud][provider]", "[host][id]", "[host][ip]", "[host][name]", "[host][mac]" ] }
     mutate { remove_field => [ "[cloud][instance][id]", "[cloud][image][id]", "[cloud][machine][type]", "[cloud][service][name]", "[cloud][account][id]", "[host][os][codename]", "[host][os][family]", "[host][os][kernel]", "[host][os][name]", "[host][os][platform]", "[host][os][type]", "[host][os][version]", "[cloud][instance][name]" ] }
 }
}

output {
 if [log][file][path] in ["/var/log/apache2/sfsite-access_log","/var/log/apache2/sfapi-access_log"] {
  elasticsearch {
    hosts => ["https://172.a.a.a.:9200"]
    index => "orchid-sf-%{+YYYY.MM.dd}"
    user => "elastic"
    password => "ppppp"
    ssl => true
    cacert => "/etc/logstash/http_ca.crt"
  }
}
else if [log][file][path] in ["/var/log/apache2/sfsite-error_log","/var/log/apache2/sfapi-error_log"] {
  elasticsearch {
    hosts => ["https://172.a.a.a:9200"]
    index => "orchid-sf-%{+YYYY.MM.dd}"
    user => "elastic"
    password => "pppppp"
    ssl => true
    cacert => "/etc/logstash/http_ca.crt"
  }
}
}
=====================================================================
Filebeat Apache module: (apache.yml)
# Module: apache
# Docs: https://www.elastic.co/guide/en/beats/filebeat/8.8/filebeat-module-apache.html

- module: apache
  # Access logs
  access:
    enabled: true
    var.paths: ["/var/log/apache2/sfsite-access_log", "/var/log/apache2/sfapi-access_log"]
    # Set custom paths for the log files. If left empty,
    # Filebeat will choose the paths depending on your OS.
    #var.paths:

  # Error logs
  error:
    enabled: true
    var.paths: ["/var/log/apache2/sfsite-error_log", "/var/log/apache2/sfapi-error_log"]
    # Set custom paths for the log files. If left empty,
    # Filebeat will choose the paths depending on your OS.
    #var.paths:
=======================================================================
Filebeat:(filebeat.yml)
###################### 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.

# filestream is an input for collecting log messages from files.
- type: filestream

  # Unique ID among all inputs, an ID is required.
  id: my-filestream-id

  # 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.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #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.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #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:
         host: "172.a.a.a:5601"
  # 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 `<user>:<pass>`.
#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: ["172.a.a.a: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

The above configuration was working fine for apache logs. so for can you tell me how to include cakephp logs also into this.
example:
log file path - /var/log/cakelog/demo/error.log
sample cake log like below:

2023-07-26 04:35:45 Error: [BadRequestException] Invalid Store
Request URL: /
Stack Trace:
#0 /var/www/build/storefront/storefront-516/app/Controller/AppController.php(76): AppController->checkStore()
#1 /var/www/build/storefront/storefront-516/app/Controller/SiteController.php(25): AppController->beforeFilter()
#2 /var/www/build/storefront/storefront-516/lib/Cake/Event/CakeEventManager.php(243): SiteController->beforeFilter()
#3 /var/www/build/storefront/storefront-516/lib/Cake/Controller/Controller.php(682): CakeEventManager->dispatch()
#4 /var/www/build/storefront/storefront-516/lib/Cake/Routing/Dispatcher.php(189): Controller->startupProcess()
#5 /var/www/build/storefront/storefront-516/lib/Cake/Routing/Dispatcher.php(167): Dispatcher->_invoke()
#6 /var/www/build/storefront/storefront-516/app/webroot/index.php(114): Dispatcher->dispatch()
#7 {main}
2023-07-26 04:36:45 Error: [BadRequestException] Invalid Store
Request URL: /
Stack Trace:
#0 /var/www/build/storefront/storefront-516/app/Controller/AppController.php(76): AppController->checkStore()
#1 /var/www/build/storefront/storefront-516/app/Controller/SiteController.php(25): AppController->beforeFilter()
#2 /var/www/build/storefront/storefront-516/lib/Cake/Event/CakeEventManager.php(243): SiteController->beforeFilter()
#3 /var/www/build/storefront/storefront-516/lib/Cake/Controller/Controller.php(682): CakeEventManager->dispatch()
#4 /var/www/build/storefront/storefront-516/lib/Cake/Routing/Dispatcher.php(189): Controller->startupProcess()
#5 /var/www/build/storefront/storefront-516/lib/Cake/Routing/Dispatcher.php(167): Dispatcher->_invoke()
#6 /var/www/build/storefront/storefront-516/app/webroot/index.php(114): Dispatcher->dispatch()
#7 {main}

Thanks

31

You just need to add and else here... ^^^ look at your logic you are only sending those 2 types to elastic and an else or another else if... for the cake logs... This is simple if / else logic

Pro tip if you tags that cake filebeat input then you can just us that in the output section in the logstash for the if / else

just add

filebeat.inputs:
- type: filestream
  . . .
  tags: ["cake-logs"]

Somethign like you might need to check

else if "cake-logs" in [tags] {
  elasticsearch {
    hosts => ["https://172.a.a.a:9200"]
    index => "cake-logs-%{+YYYY.MM.dd}"
    user => "elastic"
    password => "pppppp"
    ssl => true
    cacert => "/etc/logstash/http_ca.crt"
  }

Once you see them in elastic if you want to work / parse etc then you can put more logic in the filter section of the logstash conf

32

@stephenb

Thank you for your quick responses. I have three doubt's here,

  1. Where do i need to mention the cake logs file path... In the filebeat.yml or in the apache. yml file. If it's in the filebeat.yml file do I need to enable the option from false to true..!

  2. If it's in the filebeat. yml, than i already configured the apache logs via module. So is both will work...!

  3. my cake logs are multiline logs as i mentioned above.. So is that work well?

Thanks.

33

Roll up you sleeves and get to it!

I have given you enough :slight_smile:

There is no try ... only do!

34

@stephenb

Thanks a lot. My all the logs configurations was working as I expected. once again thank you very much.

35

Thank you very much for your response. I have multiple sets of errors. Whenever I receive error logs in this file, I need to send them to the Kibana data view. Could you please guide me on how to configure the Apache logs using the Apache module?

.

36

Hi @Carl_Newkirk
Welcome to the community.

Take a look here

37

Thank you..

38

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.