# Charc Set in Logstash

**URL:** <https://discuss.elastic.co/t/charc-set-in-logstash/160907>\
**Category:** Logstash\
**Created:** [December 14, 2018, 1:17pm UTC](https://discuss.elastic.co/t/charc-set-in-logstash/160907 "2018-12-14T13:17:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carlos\_Magalhaes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_magalhaes/32/74604_2.png) [@Carlos\_Magalhaes](https://discuss.elastic.co/u/Carlos_Magalhaes)\
**Post date:** [December 14, 2018, 1:17pm UTC](https://discuss.elastic.co/t/charc-set-in-logstash/160907/1 "2018-12-14T13:17:19Z")

</div>

Hi all,

Finally got some grok filters working well for some custom snort logs. Quite often it fails due to the fact that in the message or the entire message has what I assume is either:

1. Some unknown ASCII Charc
2. Encrypted traffic

Example of the data:  
�E�a@�����Ÿ�I�5�.�]ք�

Anyone handled this before either the unknown Charc set or how to handle (by handle I mean maybe set a tag saying encrypted) this type of "text".

Right now any thing that doesnt match about 8 different grok patterns gets a \_Failure\_Matching tag so I can filter them out in Kibana dashboard.

Would really help get some insight

---

<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:** [January 11, 2019, 1:17pm UTC](https://discuss.elastic.co/t/charc-set-in-logstash/160907/2 "2019-01-11T13:17:22Z")

</div>

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