# Module processor being cached?

**URL:** <https://discuss.elastic.co/t/module-processor-being-cached/99604>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 6, 2017, 2:49pm UTC](https://discuss.elastic.co/t/module-processor-being-cached/99604 "2017-09-06T14:49:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![danimaiochi](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@danimaiochi](https://discuss.elastic.co/u/danimaiochi)\
**Post date:** [September 6, 2017, 2:49pm UTC](https://discuss.elastic.co/t/module-processor-being-cached/99604/1 "2017-09-06T14:49:45Z")

</div>

Hi!  
I'm developing a new module for filebeat that I'm calling ruby.  
I noticed that my pipeline keeps using the same processor pattern it was configured on the first version.  
this is the first version of my module:

```
"processors": [
{
  "grok": {
    "field": "message",
    "patterns": [
      "%{NUMBER:ruby.requests.timestamp}"
    ]
  }
}
]

```

so since I was using NUMBER for the timestamp I got the timestamp field = "02" - OK, THAT'S EXPECTED! I'M HUMAN

after noticing that I changed for:

```
"processors": [
{
  "grok": {
    "field": "message",
    "patterns": [
      "%{TIMESTAMP_ISO8601:ruby.requests.timestamp}"
    ]
  }
}
]

```

but I still got just the last number.  
I added, changed and removed fields but keep getting the same result!

later I changed my modules/ruby folder to modules/ruby2 (and the filebeat.yml to use ruby2) and voila! it worked!

That's why I think there's some sort of cache being held and is not loading my patter everytime.  
can you guys help me with that?  
there's some sort of config to disable or a way to clear this "cache" thing?

Thanks in advance!  
(Yeah, I restarted both services after changing the processor, even rebooted the computer)  
(using windows 😣)

---

<div class="post-metadata">

**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\
**Post date:** [September 7, 2017, 12:15pm UTC](https://discuss.elastic.co/t/module-processor-being-cached/99604/2 "2017-09-07T12:15:46Z")

</div>

By default templates are not updated automatically. It must be set in `setup.template.overwrite` option to `true`. Or you can delete it manually by using Kibana's Dev tools or CURL (see: [https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-templates.html#delete](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-templates.html#delete)).

---

<div class="post-metadata">

**Author:** ![danimaiochi](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@danimaiochi](https://discuss.elastic.co/u/danimaiochi)\
**Post date:** [September 7, 2017, 1:30pm UTC](https://discuss.elastic.co/t/module-processor-being-cached/99604/3 "2017-09-07T13:30:19Z")

</div>

> [@kvch](#):
>
> setup.template.overwrite

the problem isn't with the template (btw, I'm using `setup.template.overwrite ` already)  
the problem is that Filebeat keeps using the old grok pattern.

if I have the:

```
"patterns": [
  "%{TIMESTAMP_ISO8601:ruby.requests.timestamp}"
]

```

my ruby.requests.timestamp will be like `2017-09-07 14:29:30`

and if I change the grok to

```
"patterns": [
  "lalalalalala"
]

```

instead of getting an error, I'll get the same result

---

<div class="post-metadata">

**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\
**Post date:** [September 7, 2017, 10:36pm UTC](https://discuss.elastic.co/t/module-processor-being-cached/99604/4 "2017-09-07T22:36:54Z")

</div>

Then you pipeline is not updated. Pipelines can be deleted manually using the Dev tools of Kibana using `DELETE _ingest/pipeline/your-pipeline-id`. See "more": [https://www.elastic.co/guide/en/elasticsearch/reference/current/delete-pipeline-api.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/delete-pipeline-api.html)

Also, developing grok expressions could be easier using Simulate Pipeline API. More info on it: [https://www.elastic.co/guide/en/elasticsearch/reference/5.5/simulate-pipeline-api.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/simulate-pipeline-api.html)

---

<div class="post-metadata">

**Author:** ![danimaiochi](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@danimaiochi](https://discuss.elastic.co/u/danimaiochi)\
**Post date:** [September 8, 2017, 10:13am UTC](https://discuss.elastic.co/t/module-processor-being-cached/99604/5 "2017-09-08T10:13:44Z")

</div>

yeap!  
exactly what I was looking for, I deleted the pipelines and it worked 😃

there's a way to always replace the pipeline?

Thank you so much Noémi!

---

<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:** [October 6, 2017, 10:14am UTC](https://discuss.elastic.co/t/module-processor-being-cached/99604/6 "2017-10-06T10:14:25Z")

</div>

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