# Reporting the most common log errors with Logstash 2.3.4

**URL:** https://discuss.elastic.co/t/reporting-the-most-common-log-errors-with-logstash-2-3-4/60750
**Category:** Kibana
**Created:** [September 16, 2016, 8:07pm UTC](https://discuss.elastic.co/t/reporting-the-most-common-log-errors-with-logstash-2-3-4/60750 "2016-09-16T20:07:41Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![KIVagant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kivagant/32/7182_2.png) [@KIVagant](https://discuss.elastic.co/u/KIVagant)
#### Post date: [September 19, 2016, 2:42pm UTC](https://discuss.elastic.co/t/reporting-the-most-common-log-errors-with-logstash-2-3-4/60750/10 "2016-09-19T14:42:38Z")

</div>

Hello, @Joe_Fleming

Today I have added [a new field](https://discuss.elastic.co/t/how-to-make-hash-sum-from-string/60897/2) "message\_sha1" to logstash configuration.

And when I change my data table field from "msg.raw" to "message\_sha1.raw", I see all rows. But if I add yet another sub-aggregation level by "msg.raw" field, the rows with a big length of "msg.raw" are disappearing.

So, I think, the main problem is a length of "msg.raw".

---

_[View the full topic](https://discuss.elastic.co/t/reporting-the-most-common-log-errors-with-logstash-2-3-4/60750)._