# How to deal with double type fields?

**URL:** <https://discuss.elastic.co/t/how-to-deal-with-double-type-fields/104491>\
**Category:** Logstash\
**Created:** [October 19, 2017, 6:08am UTC](https://discuss.elastic.co/t/how-to-deal-with-double-type-fields/104491 "2017-10-19T06:08:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sjaak01](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@Sjaak01](https://discuss.elastic.co/u/Sjaak01)\
**Post date:** [October 19, 2017, 6:08am UTC](https://discuss.elastic.co/t/how-to-deal-with-double-type-fields/104491/1 "2017-10-19T06:08:10Z")

</div>

Hi,

I'm still trying to get my Fortigate logs to parse correctly. I've ran into a new problem: double type fields. I use the type field to identify my logs but the Fortigate logs itself also have a type field.

Once I try parsing the recorded logs that leads to errors.

How can I best handle this?

I tried replacing my type "fortigate" with tags/id "fortigate" but when I do that my logs are not recorded anymore.

---

<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:** [November 16, 2017, 6:08am UTC](https://discuss.elastic.co/t/how-to-deal-with-double-type-fields/104491/2 "2017-11-16T06:08:19Z")

</div>

Closed on November 16, 2017, 6:08am UTC

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