# Logstash Configuration when removing specified type mapping

**URL:** <https://discuss.elastic.co/t/logstash-configuration-when-removing-specified-type-mapping/156148>\
**Category:** Logstash\
**Created:** [November 10, 2018, 3:59pm UTC](https://discuss.elastic.co/t/logstash-configuration-when-removing-specified-type-mapping/156148 "2018-11-10T15:59:56Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Makra](https://avatars.discourse-cdn.com/v4/letter/m/8491ac/32.png) [@Makra](https://discuss.elastic.co/u/Makra)\
**Post date:** [November 10, 2018, 5:42pm UTC](https://discuss.elastic.co/t/logstash-configuration-when-removing-specified-type-mapping/156148/5 "2018-11-10T17:42:11Z")

</div>

Your answer is here

> [@How to tag log files in filebeat for logstash ingestion?](https://discuss.elastic.co/t/how-to-tag-log-files-in-filebeat-for-logstash-ingestion/44713/6):
>
> Digging deeper, it seems like I should be able to say: type =\> "%{[@metadata][log\_type]}" or would it be type =\>"%{[log\_type]}" Or if I were trying to use the source field, using: type =\> "%{[@metadata][source]}" Does that look right? Is that how I would access a field within logstash, so that I can appropriately type the data within the input?

---

_[View the full topic](https://discuss.elastic.co/t/logstash-configuration-when-removing-specified-type-mapping/156148)._