# New custom beat is not sending a template mapping

**URL:** <https://discuss.elastic.co/t/new-custom-beat-is-not-sending-a-template-mapping/186310>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [June 18, 2019, 4:17pm UTC](https://discuss.elastic.co/t/new-custom-beat-is-not-sending-a-template-mapping/186310 "2019-06-18T16:17:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hmschreck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hmschreck/32/49405_2.png) [@hmschreck](https://discuss.elastic.co/u/hmschreck)\
**Post date:** [June 18, 2019, 4:17pm UTC](https://discuss.elastic.co/t/new-custom-beat-is-not-sending-a-template-mapping/186310/1 "2019-06-18T16:17:24Z")

</div>

I am creating a custom beat, and I have things such as the follow in `_meta/fields.yml`

```auto
    - name: port_22_out
      type: integer

```

When I run the built beat, it is not sending a mapping, as evidenced by the following `mapping` in the index in Kibana:

```auto
{
  "mapping": {}
}

```

There is not a json template file in here anywhere - what am I missing?

---

<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:** [June 25, 2019, 4:50pm UTC](https://discuss.elastic.co/t/new-custom-beat-is-not-sending-a-template-mapping/186310/2 "2019-06-25T16:50:05Z")

</div>

Have you run `make update`, so the appropriate `include/fields.go` is generated?

---

<div class="post-metadata">

**Author:** ![hmschreck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hmschreck/32/49405_2.png) [@hmschreck](https://discuss.elastic.co/u/hmschreck)\
**Post date:** [June 27, 2019, 4:48pm UTC](https://discuss.elastic.co/t/new-custom-beat-is-not-sending-a-template-mapping/186310/3 "2019-06-27T16:48:39Z")

</div>

I have! My current workaround is to forcibly overwrite using fields.yml, but that feels really gross.

---

<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:** [June 28, 2019, 11:40am UTC](https://discuss.elastic.co/t/new-custom-beat-is-not-sending-a-template-mapping/186310/4 "2019-06-28T11:40:11Z")

</div>

What do you mean by forcibly overwrite using fields.yml?

---

<div class="post-metadata">

**Author:** ![hmschreck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hmschreck/32/49405_2.png) [@hmschreck](https://discuss.elastic.co/u/hmschreck)\
**Post date:** [June 28, 2019, 6:42pm UTC](https://discuss.elastic.co/t/new-custom-beat-is-not-sending-a-template-mapping/186310/5 "2019-06-28T18:42:00Z")

</div>

If I set "setup.template.overwrite: true" and specify the freshly generated fields.yml, it works fine.

---

<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:** [July 26, 2019, 6:42pm UTC](https://discuss.elastic.co/t/new-custom-beat-is-not-sending-a-template-mapping/186310/6 "2019-07-26T18:42:01Z")

</div>

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