# Beats Field Data

**URL:** <https://discuss.elastic.co/t/beats-field-data/38179>\
**Category:** Beats\
**Created:** [December 30, 2015, 2:06pm UTC](https://discuss.elastic.co/t/beats-field-data/38179 "2015-12-30T14:06:30Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [December 30, 2015, 2:06pm UTC](https://discuss.elastic.co/t/beats-field-data/38179/1 "2015-12-30T14:06:30Z")

</div>

Hi,  
In the "fields" defintions of filebeat.yml is nesting permitted as follows:

fields:  
field\_type:  
sub\_type1: value  
sub\_type2: value

...which I would then reference in logstash as [fields][field\_type][sub\_type1].

Regards,  
David

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [December 30, 2015, 2:31pm UTC](https://discuss.elastic.co/t/beats-field-data/38179/2 "2015-12-30T14:31:08Z")

</div>

Hi David

Is that a conclusion or a question? It was introduced recently here [https://github.com/elastic/beats/pull/506](https://github.com/elastic/beats/pull/506)

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [December 30, 2015, 3:01pm UTC](https://discuss.elastic.co/t/beats-field-data/38179/3 "2015-12-30T15:01:33Z")

</div>

It was a grammatically poor question. But thanks for the confirmation 🙂

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [December 31, 2015, 9:45am UTC](https://discuss.elastic.co/t/beats-field-data/38179/4 "2015-12-31T09:45:52Z")

</div>

I'm getting errors when I try this. My config looks like this:

```
  fields:
    cluster:
      name: <name> 
      zone: <zone>
    node:
      role: <role>
      storage: <store>
    business:
      company: <company>

```

The error i get is:

2015/12/31 09:42:30.572496 beat.go:107: INFO Init Beat: filebeat; Version: 1.0.1  
2015/12/31 09:42:30.573299 main.go:42: CRIT Config error: Error reading config file: YAML config parsing failed on /etc/filebeat/filebeat.yml: yaml: unmarshal errors:  
line 40: cannot unmarshal !!map into string  
line 43: cannot unmarshal !!map into string  
line 46: cannot unmarshal !!map into string. Exiting.  
...fail!

The lines referenced correspond to fields,[cluster.name](http://cluster.name), fields,node.role and fields.business.company. How should I be structuring this?

Regards,  
David

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [December 31, 2015, 4:34pm UTC](https://discuss.elastic.co/t/beats-field-data/38179/5 "2015-12-31T16:34:20Z")

</div>

I actually get the same output when I test it on my machine. @magnusbaeck What is the format that has to be used?

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [January 4, 2016, 10:20am UTC](https://discuss.elastic.co/t/beats-field-data/38179/6 "2016-01-04T10:20:26Z")

</div>

@dawiro I just checked the same config with master and it seems to work. I have to check if some changes perhaps not made it into 1.0.1. Could you try with one of the nightlies? [https://beats-nightlies.s3.amazonaws.com/index.html?prefix=filebeat/](https://beats-nightlies.s3.amazonaws.com/index.html?prefix=filebeat/)

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [January 4, 2016, 11:02am UTC](https://discuss.elastic.co/t/beats-field-data/38179/7 "2016-01-04T11:02:00Z")

</div>

@dawiro Checked in detail and this is not part of 1.0.1 yet (sorry for the confusion). The feature is available in the 1.1 snapshots.

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [January 4, 2016, 11:07am UTC](https://discuss.elastic.co/t/beats-field-data/38179/8 "2016-01-04T11:07:37Z")

</div>

When is 1.1 due to be released?

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [January 4, 2016, 11:15am UTC](https://discuss.elastic.co/t/beats-field-data/38179/9 "2016-01-04T11:15:22Z")

</div>

It is currently planned for mid/end January, but the snapshot should be stable already.

---

<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 5, 2017, 9:57pm UTC](https://discuss.elastic.co/t/beats-field-data/38179/10 "2017-07-05T21:57:05Z")

</div>