# Kubernetes custom pipeline processing

**URL:** https://discuss.elastic.co/t/kubernetes-custom-pipeline-processing/333946
**Category:** Beats
**Tags:** filebeat
**Created:** [May 21, 2023, 1:46pm UTC](https://discuss.elastic.co/t/kubernetes-custom-pipeline-processing/333946 "2023-05-21T13:46:46Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Vijayakumar\_Kannan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijayakumar_kannan/32/34873_2.png) [@Vijayakumar\_Kannan](https://discuss.elastic.co/u/Vijayakumar_Kannan)
#### Post date: [May 21, 2023, 1:46pm UTC](https://discuss.elastic.co/t/kubernetes-custom-pipeline-processing/333946/1 "2023-05-21T13:46:46Z")

</div>

In pod following annotations mentioned but pipeline is not processing.

```auto
      annotations:
        co.elastic.logs/enabled: 'true'
        co.elastic.logs/fileset: syslog
        co.elastic.logs/module: system
        co.elastic.logs/pipeline: filebeat-kube-java-logs

```

Filebeat daemonset configuration

```auto
  filebeat.yml: |-
    filebeat.autodiscover: 
      providers:
        - type: kubernetes
          hints.enabled: true
          hints.default_config:
            type: container
            paths:
              - /var/log/containers/*-${data.kubernetes.container.id}.log
          templates:
            - condition:
                equals:
                  kubernetes.namespace: "jboss-eap-test1"
              config:
                - type: container
                  paths:
                    - /var/log/containers/*-${data.kubernetes.container.id}.log
                  pipeline: filebeat-eis-java-logs

    processors:
      - add_cloud_metadata:
      - add_host_metadata:
      - add_kubernetes_metadata:

```

The pod is processed by hint based autodiscover. I had checked the multiline annotations that's also working only pipeline not working.

---

<div class="post-metadata">

### 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: [May 21, 2023, 2:24pm UTC](https://discuss.elastic.co/t/kubernetes-custom-pipeline-processing/333946/2 "2023-05-21T14:24:46Z")

</div>

What version?

Are you sure the pipeline is not running or is it perhaps failing?.

What I always do is just create a pipeline with a simple `set` field to see if it's running or not.

I'm also confused because you said you checked multi-line but I don't see anything from multiline so I'm not really clear.

It is also not clear whether you mean just the one on the top is not running or your default template is not running or both?

---

<div class="post-metadata">

### Author: ![Vijayakumar\_Kannan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijayakumar_kannan/32/34873_2.png) [@Vijayakumar\_Kannan](https://discuss.elastic.co/u/Vijayakumar_Kannan)
#### Post date: [May 22, 2023, 5:46am UTC](https://discuss.elastic.co/t/kubernetes-custom-pipeline-processing/333946/3 "2023-05-22T05:46:36Z")

</div>

I am using the version of **7.16.0** of filebeat version. While i was troubleshooting i had enabled the multiline pattern annotations to check and eliminate the annotations indeed picked up by hint based autodiscover. It worked so i removed multiline annotations from pod config ...

1. Checked pipeline passing through the **template**. it's not working .
2. Checked the pipeline passing through the **annotations**. it's not working.

# Pipeline

```auto
PUT _ingest/pipeline/filebeat-kube-java-logs
{
    "description" : "Java EIS logs",
    "processors" : [
{
  "set": {
    "field": "kubetext",
    "value": "i'm ok"
  }
}
    ]
  }

```

---

<div class="post-metadata">

### 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: [May 22, 2023, 3:27pm UTC](https://discuss.elastic.co/t/kubernetes-custom-pipeline-processing/333946/4 "2023-05-22T15:27:29Z")

</div>

Hi @Vijayakumar_Kannan

Hmm I am taking a look may take a little while to get back.

---

<div class="post-metadata">

### 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: [May 22, 2023, 5:44pm UTC](https://discuss.elastic.co/t/kubernetes-custom-pipeline-processing/333946/5 "2023-05-22T17:44:50Z")

</div>

@Vijayakumar_Kannan

Found it... `pipeline` hint was not introduced until 8.1 you are on 7.16 really important to look at the right docs version.

You will see in 7.16 that the `pipeline` hint is not available.

Took me a while to figure it out. I tried 8.1+ and it works....

---

<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: [June 19, 2023, 7:45pm UTC](https://discuss.elastic.co/t/kubernetes-custom-pipeline-processing/333946/6 "2023-06-19T19:45:24Z")

</div>

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