# Filebeat Kubernetes autodiscover with post "processor" specific field with another filebeat module

**URL:** <https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 5, 2023, 3:29am UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503 "2023-01-05T03:29:54Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![kgfathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kgfathur/32/79353_2.png) [@kgfathur](https://discuss.elastic.co/u/kgfathur)\
**Post date:** [January 5, 2023, 3:29am UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/1 "2023-01-05T03:29:54Z")

</div>

I have setup filbeat on Kubernetes (ECK) with sample and guide from docs:

- [Role Based Access Control for Beats | Elastic Cloud on Kubernetes [2.5] ](https://www.elastic.co/guide/en/cloud-on-k8s/2.5/k8s-beat-configuration.html#k8s-beat-role-based-access-control-for-beats)
- [Run Filebeat on Kubernetes | Filebeat Reference [8.5] ](https://www.elastic.co/guide/en/beats/filebeat/8.5/running-on-kubernetes.html)

**Version:**  
ECK: 2.5.0  
filebeat: 8.5.3

The filebeat deployment and configuration already running.  
Here's some manifest snipet that used for deploy the filebeat:

```auto
$ cat filebeat-eck.autodiscover.yaml
apiVersion: beat.k8s.elastic.co/v1beta1
kind: Beat
metadata:
  name: elastic
spec:
  type: filebeat
  version: 8.5.3
  elasticsearchRef:
    name: elastic
  config:
    filebeat:
      autodiscover:
        providers:
        - node: ${NODE_NAME}
          type: kubernetes
          hints:
            enabled: true
            default_config:
              type: container
              paths:
              - /var/log/containers/*${data.kubernetes.container.id}.log
  daemonSet:
    podTemplate:
      spec:
        dnsPolicy: ClusterFirstWithHostNet
        hostNetwork: true
        securityContext:
          runAsUser: 0
...

```

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/2/92e7d46e3d453c09a8beff07c3c9f8a58770e697.png)

Kubernetes logs has been successfully parsed. However, In the image example, I have specified Apps/Pod that running NGINX and I want to process the "message" field with NGINX filebeat module. Since the "message" field is exactly match the filebeat module for NGINX.

I've read some possible feature realated to "processor" in the filebeat.

- [Filter and enhance data with processors| Filebeat Reference [8.5]](https://www.elastic.co/guide/en/beats/filebeat/8.5/filtering-and-enhancing-data.html)

The document said that:

```auto
The libbeat library provides processors for:
- reducing the number of exported fields
- enhancing events with additional metadata-
- performing additional processing and decoding

```

So it can be used for **performing additional processing and decoding**. it's amazing feature.

```auto
event -> processor 1 -> event1 -> processor 2 -> event2 ...

```

However, from the docs I can assume that it can process event with pre-defined/supported "processor":

- [Processors | Filebeat Reference [8.5]](https://www.elastic.co/guide/en/beats/filebeat/8.5/defining-processors.html#processors)
- [Dissect strings | Filebeat Reference [8.5]](https://www.elastic.co/guide/en/beats/filebeat/8.5/dissect.html)

I see a there's "dissect" processor that can be used to add custom enrich for specific field (Like we can use with logstash). However, the custom filter/grok actually is not what's expected here, since the filebeat itself has many of built-in module (that include pipeline/filter), i.e: nginx.

Is that possible to do something like this?

```auto
[module] -> [event] -> [processor] ( to process specific field with antother filebeat module) -> [event] -> ...

```

I have considered for post-processing with Logstash. However, if that's possible to be done in filebeat using pre-define modulle/processor it would be better.

I've take a look some possible feature:

- [Hints based autodiscover | Filebeat Reference [8.5] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/8.5/configuration-autodiscover-hints.html)
- [Example: Parse logs in the Common Log Format | Elasticsearch Guide [8.5] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.5/common-log-format-example.html)

If there's more best practice to do this, or any help and suggestions would be greatly appreciated!

Thanks! 🙂

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [January 5, 2023, 1:23pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/2 "2023-01-05T13:23:37Z")

</div>

Yes, u can use the hints to apply module specific paying to container logs. You can also specify in the auto discover section of the config as seen here [Autodiscover | Filebeat Reference [8.5] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-autodiscover.html)

---

<div class="post-metadata">

**Author:** ![kgfathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kgfathur/32/79353_2.png) [@kgfathur](https://discuss.elastic.co/u/kgfathur)\
**Post date:** [January 6, 2023, 6:27am UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/3 "2023-01-06T06:27:04Z")

</div>

Thanks Alex, for the suggestion.

I'm still reading the docs, and trying to understand it 😃  
After more than 10hrs, take a rest and read it again, just find that there's "hint" that we can use on the pod annotations.

---

<div class="post-metadata">

**Author:** ![Ayush\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayush_mathur/32/77134_2.png) [@Ayush\_Mathur](https://discuss.elastic.co/u/Ayush_Mathur)\
**Post date:** [January 6, 2023, 2:10pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/4 "2023-01-06T14:10:29Z")

</div>

@kgfathur or you can configure filebeat input for nginx if you want to keep the autodiscovery simple 🙂

---

<div class="post-metadata">

**Author:** ![kgfathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kgfathur/32/79353_2.png) [@kgfathur](https://discuss.elastic.co/u/kgfathur)\
**Post date:** [January 6, 2023, 3:34pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/5 "2023-01-06T15:34:33Z")

</div>

Thanks all, for the recommendation and suggestion.

Finally the pod/container logs from specific log format has been perfectly parsed using [Hints based autodiscover | Filebeat Reference [8.5] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-autodiscover-hints.html#configuration-autodiscover-hints).

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/1/11b7617ccbcd61d7632320791faf15cb9e4f450e.png)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/2/62a932b8e555417509f81314e1a2289b37c8427b.png)

In the first time read the docs, I don't get the point on how to put the "hint" that parsed the log from kubernetes pod/container with different module.  
The key are "annotations" (for kubernetes) or "labels" (for container/docker/podman etc)  
In my case, on kubernetes, every pod/container log that need to be processed by the filebeat module/pipeline, So I need add some annotations. For `Deployment` we can create sample manifest like this:

```auto
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: webapp-deployment
spec:
  selector:
    matchLabels:
      app: webapp
  replicas: 2
  template:
    metadata:
      labels:
        app: webapp
      annotations:
        co.elastic.logs/module: nginx
        co.elastic.logs/fileset.stdout: access
        co.elastic.logs/fileset.stderr: error
    spec:
      containers:
      - name: webapp
        image: nginx:1.22.1
        ports:
        - containerPort: 80

```

Hope that help someone out there! 😃

---

<div class="post-metadata">

**Author:** ![kgfathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kgfathur/32/79353_2.png) [@kgfathur](https://discuss.elastic.co/u/kgfathur)\
**Post date:** [January 6, 2023, 3:44pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/6 "2023-01-06T15:44:36Z")

</div>

Do you mean the filebeat nginx module directly read the access/error log file?

Or something like this? [NGINX Ingress controller + Filebeat with NGINX module - Elastic Stack / Beats - Discuss the Elastic Stack](https://discuss.elastic.co/t/nginx-ingress-controller-filebeat-with-nginx-module/291824)

---

<div class="post-metadata">

**Author:** ![Ayush\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayush_mathur/32/77134_2.png) [@Ayush\_Mathur](https://discuss.elastic.co/u/Ayush_Mathur)\
**Post date:** [January 6, 2023, 3:48pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/7 "2023-01-06T15:48:27Z")

</div>

My idea was to use the nginx module directly as shown here: [Nginx module | Filebeat Reference [8.5] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-nginx.html)

---

<div class="post-metadata">

**Author:** ![kgfathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kgfathur/32/79353_2.png) [@kgfathur](https://discuss.elastic.co/u/kgfathur)\
**Post date:** [January 6, 2023, 4:03pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/8 "2023-01-06T16:03:09Z")

</div>

Thanks for the Ideas!  
However, I don't know if that will be easy to setup, since the logs come from containers that running on top kubernetes. So the log actually have some additional information and format.  
The file also get merged between `access.log` (stdout) and `error.log` (stderr).

```auto
root@worker04:/var/log/pods# ls -lh
total 80K
...
drwxr-xr-x 3 root root 4.0K Jan 6 13:49 sample-webapp_webapp-deployment-f7c5c5596-jzhvr_3c360017-b15c-46d7-8da0-dd842f0bbc8e
root@worker04:/var/log/pods# ls -lh sample-webapp_webapp-deployment-f7c5c5596-jzhvr_3c360017-b15c-46d7-8da0-dd842f0bbc8e/
total 4.0K
drwxr-xr-x 2 root root 4.0K Jan 6 13:49 webapp
root@worker04:/var/log/pods# ls -lh sample-webapp_webapp-deployment-f7c5c5596-jzhvr_3c360017-b15c-46d7-8da0-dd842f0bbc8e/webapp/
total 4.1M
-rw------- 1 root root 4.1M Jan 6 15:54 0.log
root@worker04:/var/log/pods#

```

there's just 1 log for the standard nginx container/pod. The `access` and `error` log has been placed into 1 file.

The log also has different format, it's follow standard kubernetes log prefix, I think.

```auto
root@worker04:/var/log/pods# head -n5 sample-webapp_webapp-deployment-f7c5c5596-jzhvr_3c360017-b15c-46d7-8da0-dd842f0bbc8e/webapp/0.log
2023-01-06T13:49:43.865470598+00:00 stdout F /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
2023-01-06T13:49:43.865470598+00:00 stdout F /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
2023-01-06T13:49:43.866624107+00:00 stdout F /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
2023-01-06T13:49:43.871137409+00:00 stdout F 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
2023-01-06T13:49:43.877291349+00:00 stdout F 10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
root@worker04:/var/log/pods#
root@worker04:/var/log/pods# tail -n5 sample-webapp_webapp-deployment-f7c5c5596-jzhvr_3c360017-b15c-46d7-8da0-dd842f0bbc8e/webapp/0.log
2023-01-06T15:59:56.943756171+00:00 stdout F webapp.apps.k8s.domain.lab 10.16.0.147 - - [06/Jan/2023:15:59:56 +0000] "GET / HTTP/1.1" 200 615 "-" "curl/7.61.1" "10.8.60.9"
2023-01-06T15:59:57.065568724+00:00 stdout F webapp.apps.k8s.domain.lab 10.16.0.147 - - [06/Jan/2023:15:59:57 +0000] "GET / HTTP/1.1" 200 615 "-" "curl/7.61.1" "10.8.60.9"
2023-01-06T15:59:57.187069588+00:00 stdout F webapp.apps.k8s.domain.lab 10.16.0.147 - - [06/Jan/2023:15:59:57 +0000] "GET / HTTP/1.1" 200 615 "-" "curl/7.61.1" "10.8.60.9"
2023-01-06T15:59:57.551829353+00:00 stdout F webapp.apps.k8s.domain.lab 10.16.0.147 - - [06/Jan/2023:15:59:57 +0000] "GET / HTTP/1.1" 200 615 "-" "curl/7.61.1" "10.8.60.9"
2023-01-06T15:59:57.674128175+00:00 stdout F webapp.apps.k8s.domain.lab 10.16.0.147 - - [06/Jan/2023:15:59:57 +0000] "GET / HTTP/1.1" 200 615 "-" "curl/7.61.1" "10.8.60.9"
root@worker04:/var/log/pods#

```

So to keep everything simple, and standard, I prefer to use Autodiscover hint.  
Because I just need to setup general autodiscover for kubernetes/containers on filebeat side. Then setup `annotation` for every pod that I want to process the log, with more flexible module and it's self services.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 3, 2023, 6:03pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-autodiscover-with-post-processor-specific-field-with-another-filebeat-module/322503/9 "2023-02-03T18:03:13Z")

</div>

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