# Filebeat Apache module not showing data on Dashboards when using Logstash

**URL:** <https://discuss.elastic.co/t/filebeat-apache-module-not-showing-data-on-dashboards-when-using-logstash/318594>\
**Category:** Elasticsearch\
**Created:** [November 9, 2022, 10:43pm UTC](https://discuss.elastic.co/t/filebeat-apache-module-not-showing-data-on-dashboards-when-using-logstash/318594 "2022-11-09T22:43:19Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [November 10, 2022, 11:08pm UTC](https://discuss.elastic.co/t/filebeat-apache-module-not-showing-data-on-dashboards-when-using-logstash/318594/13 "2022-11-10T23:08:08Z")

</div>

@leandrojmp Huh What do you know..

> <https://github.com/elastic/integrations/issues/3451>
>
> From the apache ingest pipeline (\[link\](https://github.com/elastic/integrations/…blob/main/packages/apache/data\_stream/access/elasticsearch/ingest\_pipeline/default.yml#L13-L15)):
> 
> \`\`\`yaml
> - rename:
> field: message
> target\_field: event.original
> \`\`\`
> 
> The rename processor documentation states:
> 
> \> If the field doesn’t exist or the new name is already used, an exception will be thrown.
> 
> This means that any document that already has an "event.original" field (with or without a "message") field will cause an ingestion error:
> 
> \`\`\`json
> "message": "......",
> "error": {
> "message": "field \[event.original\] already exists"
> },
> \`\`\`
> 
> A suggestion is to tolerate the presence of "event.original" and "message" fields by including an \`if\` condition in the rename processor.

Known issue this plus a couple internals etc.. .not sure when it will get fix... its one of those accross teams issue 🙂

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-apache-module-not-showing-data-on-dashboards-when-using-logstash/318594)._