# Logstash CEF codec

**URL:** <https://discuss.elastic.co/t/logstash-cef-codec/33783>\
**Category:** Logstash\
**Created:** [November 4, 2015, 7:07pm UTC](https://discuss.elastic.co/t/logstash-cef-codec/33783 "2015-11-04T19:07:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![us3r](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/us3r/32/4647_2.png) [@us3r](https://discuss.elastic.co/u/us3r)\
**Post date:** [November 4, 2015, 7:07pm UTC](https://discuss.elastic.co/t/logstash-cef-codec/33783/1 "2015-11-04T19:07:19Z")

</div>

Together with my collegue we found a few problems with this codec:

The first one is described here -\> [https://github.com/logstash-plugins/logstash-codec-cef/issues/9](https://github.com/logstash-plugins/logstash-codec-cef/issues/9)  
Second one is related with the changes in Elasticsearch 2.0 like:

```
MapperParsingException[Field name [FOO.BAR] cannot contain '.']

```

Does anyone of you have a plan to solve that?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [November 4, 2015, 7:12pm UTC](https://discuss.elastic.co/t/logstash-cef-codec/33783/2 "2015-11-04T19:12:33Z")

</div>

As documented, Elasticsearch 2.0 doesn't allow periods in field names. You'll have to rename your fields.

[https://www.elastic.co/guide/en/elasticsearch/reference/2.0/\_mapping\_changes.html#\_field\_names\_may\_not\_contain\_dots](https://www.elastic.co/guide/en/elasticsearch/reference/2.0/_mapping_changes.html#_field_names_may_not_contain_dots)

---

<div class="post-metadata">

**Author:** ![us3r](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/us3r/32/4647_2.png) [@us3r](https://discuss.elastic.co/u/us3r)\
**Post date:** [November 4, 2015, 7:19pm UTC](https://discuss.elastic.co/t/logstash-cef-codec/33783/3 "2015-11-04T19:19:26Z")

</div>

yes I know that. But maybe a good idea is to implement such kind of functionality **(properly)** directly on the codec layer.  
There is a problem with the codec itself cause some fields like "cef\_ext.whatever" are splited correctly. I have noticed this problem with for ex "ad.arcSightEventPath" field.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [November 4, 2015, 10:15pm UTC](https://discuss.elastic.co/t/logstash-cef-codec/33783/4 "2015-11-04T22:15:20Z")

</div>

Please see: [Please read: Upgrading Logstash and Elasticsearch to 2.0](https://discuss.elastic.co/t/dots-in-field-names-and-elasticsearch-2-0/33791)

---

<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 6, 2017, 5:23am UTC](https://discuss.elastic.co/t/logstash-cef-codec/33783/5 "2017-07-06T05:23:59Z")

</div>